Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!UKANVAX.BITNET!SLOANE From: SLOANE@UKANVAX.BITNET.UUCP Newsgroups: comp.os.vms Subject: Re: Contemplations on CDU Message-ID: <8706120149.AA07887@ucbvax.Berkeley.EDU> Date: Wed, 10-Jun-87 12:16:00 EDT Article-I.D.: ucbvax.8706120149.AA07887 Posted: Wed Jun 10 12:16:00 1987 Date-Received: Sat, 13-Jun-87 11:11:58 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 28 Regarding Erland Sommarskog's CLD example, the problem seems to be in the definition of the word DEFAULT. I think of DEFAULT as meaning the value that is supplied by the system WHEN NO VALUE IS GIVEN. If the user enters some value, then no DEFAULT value should be used. In the example: Define Type CHAR_NAMES Qualifier WORD_CHARS, keyword HYPHEN, default, negatable Default, keyword NUMBERS, default, negatable Nonnegatable keyword UNDERSCORE, negatable Value(Required, List, ... ! 20 more no-default and negatable Type = CHAR_NAMES) keyword ALL, nonnegatable Erland would like HYPHEN and NUMBERS to always be in the list, even though only UNDERSCORE was entered by the user, as if DEFAULT means that these values are always in the list BY DEFAULT, not that they are DEFAULT VALUES used by system when no other value is given. I think either definition is valid. Suppose, for example, that I was writing the same program as Erland, but for WORD_CHARS I wanted the default to be ALL, not HYPHEN and NUMBERS. Then the program would have to know that the ALL option should only be processed when there were no other options present. It would be nice to have it both ways, but that would mean adding an new option to CDU. In any case, I do not think that this is a bug in CDU, which was the original question. Bob Sloane University of Kansas Computer Center (913) 864-4291 SLOANE@UKANVAX on BITNET