[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

93.0. "PROFILE and subelements problem" by COOKIE::JOHNSTON () Wed Mar 11 1987 19:48

I am building/using a PROFILE for the first time.  One of the subelements
to the first chapter is a file that begins with <HEAD1>, as shown in the last
line of this example:

<ELEMENT>(EXEC_SUMMARY_CHAP.GNC)
<INCLUDES_FILE>(exec_summary_fig\EXEC_SUMMARY_FIG.GNC)
<INCLUDES_FILE>(exec_summary_tbl\EXEC_SUMMARY_TBL.GNC)
<INCLUDES_FILE>(review_issues_sec\REVIEW_ISSUES_SEC.GNC)

I process the file and get the message that the logical name review_issues_sec 
is undefined.  A REVIEW_ISSUES_SEC.TEX file is not created.  Neither does the
file show up in the .MAP. 

Included tables and figures process just fine.

Is there a problem with the way I am coding this?  Or is it not possible 
to include a "<HEAD>" file?  Or ????


Thanx

Rose

T.RTitleUserPersonal
Name
DateLines
93.1Can't reproduce the problem.VAXUUM::KOHLBRENNERThu Mar 12 1987 09:5216
    I can't reproduce that probelm here.
    
    You will never get a separate TEX files for the subelements
    that are included into an element (using <include> tags).
    A separate TEX file is produced for each element, so in this
    case you would get a TEX file for EXEC_SUMMARY_CHAP, and it will
    include all the text in EXEC_SUMMARY_CHAP.GNC and any files that
    have been read by <include> tags in EXEC_SUMMARY_CHAP.
    
    Are you sure that the <include> tag in EXEC_SUMMARY_CHAP is using
    the same logical name that is declared in the <includes_file> tag
    in the profile?
    
    If yes to the above question, send me the profile and the file that
    contains the <include> tag.
    
93.2Logicals ok, but forgot to <include>COOKIE::JOHNSTONThu Mar 12 1987 12:2016
This is embarrassing, but maybe it's just as well that it happened.
Getting egg on your face is the best way to remember not to repeat a 
mistake. The logical names all checked out; the problem was that I had
not <INCLUDE>ed EXEC_REFERENCES_SEC.GNC into EXEC_SUMMMARY_CHAP. 

Interesting question arises here, however.  In situations like this, 
should DOCUMENT produce the error "Can't find file for symbolic-name"
instead of (or along with) the "symbolic-name undefined" message? 

You see, 2 days ago that included file was a part of the chapter file 
and not separate from it.  I decided to put it in another file because 
the information in it was lengthy and stable.  I cut it from the chapter 
file, created a new file for it, built my profile, and just forgot to 
add an include tag to the chapter file.  Of course, now I'll remember to 
hunt for an <include> if this ever happens again,...gawd forbid.

93.3when to issue error messagesVAXUUM::KOHLBRENNERThu Mar 12 1987 15:5411
    Yeah, I guess a warning that "you defined this logical, but never
    used it" would have been helpful in your case.  But I could imagine
    someone complaining that "I haven't used it YET, but I intend to,
    and would you please stop telling me about it!"
    
    It's like putting a symbol on a <table> tag and then not putting
    a <reference> tag anywhere that refers to the symbol.
    
    And tying the issuance of one error message to the issuance of
    another error message is bordering on Artifical Intelligence...
    
93.4Add it to error descriptionsCOOKIE::JOHNSTONThu Mar 12 1987 20:077
When all else fails...document, document, document.

A blurb in the appendix that describes error messages would be helpful, then.



Rose