Conference vaxuum::document_ft

346.0. "pascal bug?" by NADIR::GRIGLACK () Wed May 06 1987 11:07

I have been trying to build a book using a book build file.  I get
what appears to be a pascal error message which doesn't really tell
me what the problem is or how to go about fixing it.  I have included
the .log file and the book build file.  The error is:

%PAS-F-VARINDVAL, varying index value is greater than current length
$ exit ($status + (0 * f$verify(verify_context))) ! 
SYS$SCRATCH:DOC$900709204001732BCBA180.TMP - End

    
    Can you provide an information?
    
    Thanks - 
    
    Lisa
************************************************************

here is the .log file:

$ MODETST := BATCH
$ IF MODETST  .NES. "INTERACTIVE" THEN GOTO EXIT
$ EXIT: 
$ exit
$ verify_context = 1 ! SYS$SCRATCH:DOC$900709204001732BCBA180.TMP - Start
$ d = "document"
$ set = "set"
$ set noon
$ set default work$:[dbmsdoc.v33.prog]
$ D /NOPRINT/BATCH=(NOPRINT,NOTIFY,NAME=BOOKBUILD.LOG)/CONTENTS/INDEX 308ALL VIA LN03
%DOC-I-IDENT, VAX DOCUMENT T1.0-001
[ T a g   T r a n s l a t i o n ]...
%TAG-I-TAG_IDENT, T1.0
%TAG-I-DEFSLOADD, End of Loading of Tag Definitions
%PAS-F-VARINDVAL, varying index value is greater than current length
$ exit ($status + (0 * f$verify(verify_context))) ! SYS$SCRATCH:DOC$900709204001732BCBA180.TMP - End
  GRIGLACK     job terminated at  6-MAY-1987 10:49:15.49

  Accounting information:
  Buffered I/O count:          110      Peak working set size:  1024
  Direct I/O count:            185      Peak page file size:    7711
  Page faults:                2740      Mounted volumes:           0
  Charged CPU time:     0 00:01:00.77   Elapsed time:     0 00:01:27.65

************************************************************************

here is the book build file

<profile>

<element>(308front.gnc)

<contents_file>

<element>(308ch1.gnc)
<element>(newch2.gnc)
<element>(newch3.gnc)
<element>(ch4ada.gnc)
<element>(ch5basic.gnc)
<element>(ch6bliss.gnc)
<element>(ch7c.gnc)
<element>(ch8cobol.gnc)
<element>(ch9dibol.gnc)
<element>(ch10fortran.gnc)
<element>(ch11macro.gnc)
<element>(ch12pascal.gnc)
<element>(ch13pli.gnc)
<element>(errors.gnc)

<comment>
<element>(newappa.gnc)
<element>(newappb.gnc)
<element>(newappc.gnc)
<endcomment>

<index_file>
<endprofile>

    Lisa --

    See note #128.  That message appears when you have too many nested
    tags or something.  Maybe that is happening in your case...?

							-- Nina

    I just got that same error message. In my case it was happening
    because I forgot a closing paren. I had the following statment
    <literal>(<1034>
    I was supposed to have (<1034>), but because I forgot the ) it
    just kept looking for it and I got the error message.
    
    James.

Missing parens sure cause a lot of problems.  Is there a command you can 
use in EDT, LSE, or at DCL to count and/or compare the number of ( and 
)?


Rose

    One simple way to do this in a text editor is to replace all the
    ('s with ('s and the )'s with )'s and then compare the number of
    each replaced.  If they totals don't match, you've got a mismatch
    somewhere. Of course, if do something like this <literal>(() you're
    going to throw the count off.

    Emacs has a function that, when enabled, will have the editor find
    the mate when you type a closing parenthesis. Somewhat time-consuming
    if it has to scan the whole file, but it's worth it. (You still
    have to persuade your system manager that Emacs isn't going to strangle
    your system.)
    
    kh

    When I first started using LaTeX (before XLSE supported LaTeX), I had
    chronic problems with mismatched braces.  This lead almost immediately
    to adding a parenthesis-matching feature to XLSE.  It supports the
    following pairs of characters:

	() [] {} <>

    See the CASEE::XLSE Conference for more information about XLSE.

    -- Ward

    P.S.  LSE/XLSE won't "strangle your system."

    re .6
    
    Very cute; I hadn't noticed that before. Now, if only it knew
    about BEGIN/END in BLISS...