continuing . . is functionally e
On 7/28/14, John Gilmore <[email protected]> wrote: > EJ's distinction between, say, command-language option values and > macro-instruction keyword-parameter values is not always a firm one. > > I often make a CL available for use in generating macro instructions. > Consider a simple table-gerneration situation in which, say, the macro > definition TABGEN has a usage= keyword parameter, the values of which > are > > o usage=initial, > > o usage=entry, or > > o usage=final > > If now I permit a CL user to specify in effect the value of usage= in > a macro instruction by so arranging things that any element in one of > the rows > > o i, in, ini, init, initia, initial, > > o e, en, ent, entr, entry, or > > o f, fi, fin, fina, final > > is func tionally eq > > On 7/28/14, Ed Jaffe <[email protected]> wrote: >> On 7/25/2014 8:17 AM, Paul Gilmartin wrote: >>> On 2014-07-25, at 08:40, John Gilmore wrote: >>> >>>> We disagree, sharply. The abbreviation of long keyword/set element >>>> values using the notion of a case-independent disambiguating >>>> truncation is 1) convenient and 2) easy to teach in the sense that >>>> programmers and others come to understand it quickly. >>>> >>> And here, I take Fred's side. >> >> I LOVE abbreviations for interactive commands and their operands ... and >> HATE them in any kind of source code. >> >> -- >> Edward E Jaffe >> Phoenix Software International, Inc >> 831 Parkview Drive North >> El Segundo, CA 90245 >> http://www.phoenixsoftware.com/ >> > > > -- > John Gilmore, Ashland, MA 01721 - USA > -- John Gilmore, Ashland, MA 01721 - USA
