[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::document_ft

Title:DOCUMENT T1.0
Notice:**New notesfile (DOCUMENT.NOTE) now available (see note 897)**
Moderator:CLOSET::ADLER
Created:Mon Feb 09 1987
Last Modified:Thu Oct 31 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:897
Total number of notes:4397

273.0. "<INCLUDES_FILE> meaning isn't intuitive" by COOKIE::JOHNSTON () Fri Apr 17 1987 14:36

I taught a DOCUMENT class this week to a group of CSC trainers.  One
new_user comment that I thought was worth posting was that 
<INCLUDES_FILE> is not a very descriptive tag, considering its purpose, 
which is to define a logical name for a subelement file in a profile.

I readily agreed with this observation since I also had a problem with 
it when I first started using it.

How about renaming it <LOGICAL_FILE> or something else?

I can understand why you wouldn't want to get into renaming tags yet 
again, but I think this deserves serious consideration based on the fact 
that the problem of the tag not being intuitive comes up again and 
again.

Do others have any thoughts on this?


Rose


T.RTitleUserPersonal
Name
DateLines
273.1I agreeDSSDEV::EPPESDignity, always dignityFri Apr 17 1987 17:305
     I agree that <INCLUDES_FILE> is not an intuitive tag name. 
     What about a name like <DEFINE_INCLUDED_FILE>?  Would this cause
     confusion with defining symbols?  How about something like
     <INCLUDED_FILE_NAME>?
						-- Nina
273.2Agree too. <DEFINE_FILE_SYMBOL> ?PRSIS4::BURESIMarc BURESI, @EVO, DTN 858-5395Mon Apr 20 1987 13:380
273.3<DEFINE_LOGICAL_NAME_FOR_INCLUDED_FILE>? (-:CLOSET::ADLERMon Apr 20 1987 19:571
273.4Well, meaning of .-1 is now more intuitive ;^) !PRSIS4::BURESIMarc BURESI, @EVO, DTN 858-5395Tue Apr 21 1987 04:330
273.5Close, but no cigar...COOKIE::JOHNSTONTue Apr 21 1987 15:3012
Actually, .3 says it all!  I like it, cuz even I can understand it now. 
But I hate typing all that in.  As usual, I want it all.  How about 
<DEFINE_LOGICAL_FILENAME> or <DEFINE_LOGICAL_FILESPEC>?

I'd like to get *away* from anything that has "symbol" or "include" in 
it, because that's where things start getting confusing (what's a 
symbol?  what's a logical?).



Rose

273.6Keeping one's sense of humor.VAXUUM::KOHLBRENNERTue Apr 21 1987 15:442
    I think others would like just <D>, 'cause it would
    cut down on the typing...           :-)
273.7Eye nevear mayk tiping eroarz!CLOSET::KAIKOWWed Apr 22 1987 15:035
re: 273.6

>                       -< Keeping one's sense of humor. >-

Anything more than the file spec might be considered extraneous typing by some!
273.8Another PossibilityCLOSET::ETZELMikeWed Apr 22 1987 16:482
    How about <uses_logical_name>(...\...)
    
273.9Yes, yes, yes!COOKIE::JOHNSTONFri Apr 24 1987 12:5511
Well, gee, I like <uses_logical_name>...I like most of 'em, except for 
that really long one in a previous note.  I even like <d> (also in a 
previous note)...even if someone was poking fun at this incredible 
obsession I have about saving keystrokes! (-|   <--- did I type that
right?

Cheerily,

Rose


273.10I like it tooTLE::SAVAGENeil, @Spit BrookFri Apr 24 1987 13:513
    Another vote for <USES_LOGICAL_NAME>
    
    At least 'uses' and 'name' are short words.