The following lists released versions and the bugs that are fixed for
each.  The bugs are described in present tense.

1.0.5               -- Final release for ValidSIM only.


1.0.6:13Dec85       -- Released to Beta sites for expgen and 
                       8.0 Final for ValidSIM

    Incorrect "duplicate page" error message when reading multi-page
    models for drawings which also had multi-page logic drawings. 
    (Dependent on order in which the pages are encountered.)

1.1.0:19Dec85       -- "Released" to Satya Reddy for development of compare
                        program.

    MASTER_LIBRARY directive does not work.

    SUPPRESS directive works only on compiler messages.

    SINGLE_DRAWING ON requires the "leaf" drawings to be defined.
    They should not need to be defined -- a "Drawing not found" or
    "No acceptable extension" error should result in treating the
    drawing as a non-primitive leaf for this kind of compilation.
    Additionally, the linker is reading the entire hierarchy, which
    is extremely inefficient.

    Linker interface always returns left-right bit order on pins regardless
    of the configured order.

1.1.0:23Dec85       -- "Released" to Satya Reddy for development of compare
                        program.

    When a drawing on a remote network node is remade due to a non-local
    change (such as a change to a global text macro used by it) it may
    be remade several times in a row if the remote node "time" is out
    of sync with the local node.
    { When marking a page dirty by use of current time, the "current time"
    that was used was local current time.  It is now the "current time"
    of the node upon which the page resides. }

    The PRIMITIVE compiler directive is not implemented.
    { partial fix -- pathnamed use is still not implemented, e.g.
      "PRIMITIVE 'foo';" works but "PRIMITIVE '(top foo1p)foo';"
      does not. }

    comperr can not handle single_drawing on cases.



1.1.0:20Jan86       -- Beta update and released to Satya Reddy for
                       development of "compare" using single drawing ON;

    bug (7)27b-37 BUBBLE_CHECK ON does not work.

    Compiler is not treating the drawing names in a SCALD directory as
    a case-insensitive name -- it only finds the first one if the names
    are in lower case.

    BUBBLE_CHECK is not considered as a dependency.

    bug 7f-1294 Improper error message for missing EXPR property.

    FLAG bodies are being output wherever they apper (when compiling for
    LOGIC).  They are supposed to be output only when in the root drawing.
    { Mostly a linker fix, but requires compiler support to give the
    BODY_TYPE property the IS_ET_CONTROL attribute to prevent its being
    filtered on compiler output or linker input. }


1.1.1:07Feb86       -- given to customer AIT to fix the problem that they
                       had the wrong linker (1.0.3) loaded with their sim.

    Error message for error(182) (Title prop does not match directory entry)
    is bogus -- it specifies the directory entry as the title prop, so looks
    like the error does not exist.

    Error(232) (Unable to access schema file) is too vague -- should specify
    more about what the problem (permission?, unable to run rsh?).

    Error 246 (Unable to remove file) should be a warning, not an error.

    Compiler produces "Cannot access drawing directory" message for a 
    directory for which the user has write access but for which others
    have no access.  { Fix still requires that "others" be able to traverse
    the path to the drawing directory, but the directory itself may be
    completely protected from "others" and the compiler will be able to
    access it if the user can access it or if it is owned by lib and its
    owner (lib) can access it.  The fix is untested. }

1.1.2:27Feb86 

    Compiler issues bogus error messages about not being able to access
    schema or expansion files when it should be able to. { Undid the
    previous "fix" to handle this, as it was causing the compiler to 
    become lib when it encountered a new plumbing body, and then it
    would be undable to write the expansion and schema files for the
    drawing.  The "Cannot access drawing directory" when "others" cannot
    read a directory bug is back, but is much less serious than this one. }

1.1.2:11Mar86

    Compiler complains when assertion character is omitted from an \NAC
    pin name or its corresponding \I signal.  { Fix made by tivonne -- I
    suspect that the fix requires each use of the \I signal to have the
    \NAC property to prevent issuance of the error message, which is
    reasonable. }

    Compiler disconnects signals on the FIXED 4 TAP body (from customer).
    { Body has a pass-through NWC pin.  One side was left NC, the other
      connected.  This is internally synonymed to signals connected to
      other pins.  The NC signal was "virtualized" due to properties on the
      pin.  Since NCs were ignored by synonym_actuals, the other actual on
      that pin never got synonymed to actuals on the other pins as they
      were each "synonymed" to different virtual defs of the same NC
      (which was ignored in both cases).  Fix: synonym_actuals no longer
      ignores all NCs -- only those not virtualized.  
      Choose_better_base also needed to be fixed to differentiate
      between NCs and UNNAMED signals, making the former less base.     }

1.1.3:29Apr86 -- Production release (held )

    { unknown differences with 1.1.2}
    { This release was stopped due to the 2-bit replication bug fixed for
      ValidLINKER (et) 1.1.5 }

1.2a

    Not remaking expansion files when they contain a "Drawing not found"
    (or related) error on a plumbing body, though the error has been
    "fixed" by having the compiler read  another library or SCALD directory.
    The error then persists requiring deletion of expansion or schema
    files as a workaround.  { This was originally reported as fixed for
    1.0.6, but in fact was not -- the time used to mark the page "dirty"
    was an "efs_xtime" time (some time between staring compilation and
    current time) when it should have been an "efs_time" time (current
    time).  This has now been corrected. }

    Compiler produces output files with names having more than 14 characters.
    This will not fly on the PC/AT.  
    { NOTE: this is not "fixed" in any subsequent (in time) versions labled
    1.1*.  1.1* are S32 only versions. }

    Linker emits OVERSIGHT for missing EXPR on modules that were "deleted"
    by use of the PRIMITIVE directive. { Compiler now emits ABBREV="X" on
    these which prevents the oversight message. }
    { NOTE: this is not "fixed" in any subsequent (in time) versions labled
    1.1*. }


1.2b

    Compiler is unable to write to schema files on PC/AT version quite
    often.  { Problem was with special access() impelemented in fio.c }
    
1.1.4:03Jun86 -- emergency release for AIT
    
    Bug 72f1033 (MELCO 118) was not fixed as earlier reported.  This 
    (problems with handing disjoint subranges of same signal on same
    graphical net when processing signal/pin properties) is caused
    by something other than the bug that was fixed.  (The fixed bug
    looked very simliar, but affected connectivity -- this one affects
    property processing only.)  

    Pcomp unable to write a schema file when should be able to in some
    cases where directory above the drawing directory is owned by
    someone other than the owner of the drawing directory.
    
1.1.6:16Jun86 w/ 8.0g:12Jun86 -- Final release

    Numbered NC signals are being reported in the SIGNALS section of the
    expansion file.

    Pin properties reported in PIN section though they are not properties
    of the last bit of the subscript (SCALD compiler only).

    Error calculating length of line for "welcome" messages to list files
    -- caused core dump for uVAX version (1.2x).
    
1.2d -- Beta for PC/AT, Alpha for uVAX

    { released  concurrently with release of 1.1.6 -- has all above fixes }


1.2e -- Beta release for uVAX


1.2f

    Malformed connectivity file names get cryptic error message or no message
    at all.  { Portions of the name following the page number are still
    ignored. }

    Range-check error when a long drawing type is used such as
    my drawing.foobargrbxfoobar.1.1 (resulting in foobargrbxfoobar_cn.1.1).

    Assertion failure in parsing schema files under VMS -- expects a 
    constant when seeing a minus sign on a partial time stamp.

    VMS SCALD compiler (compile -o) still using sys$scaldroot instead of
    scald$root.


1.2g -- abortive PC/AT alpha release.

    Local text macros do not work.

    { First release with P-EFS (for SCALD compiler only). }

1.2h -- alpha PC/AT release (with P-EFS for SCALD compiler)

    IORESULT error messages going to linker, causing it to give an assertion
    failure and die (a bug introduced by 1.2g).

    Local text macro "make" handling is far too conservative in its
    treatment of errors -- last page of a drawing may be compiled twice
    in a row. (Bug introduced by 1.2g).

1.2i

    WARNING message is emitted about CHIPS file not being supported,
    even though it IS supported.

    VMS version of ValidCOMPILER hangs when FATAL compiler errors occur.
    { This fix was previously attempted by closing the "pipes" regardless
    of whether they were needed.  This was not enough to close the 
    mailboxes.  This release writes a 0 length record to the pipe before
    closing it if it has not yet been written (for VAX version only). }

ValidCOMPILER 1.2j -- Temp release to Eaton for core dump
SCALD Compiler 8.0j

    Random core dump occurring during compilation of page.
    { in procedure new_numbered_token_list }

    { partial fix to mishandling of signal properties on bit lists }

ValidCOMPILER 1.2k  -- VAXstation pre-production release
SCALD Compiler 8.0k  -- Temp release to Melco

    Mishandling of signal properties on bit lists (both compilers).

    Spurious error 149 when a high asserted signal is attached to
    an unbubbled but low-asserted pin which then (inside its body)
    is connected to a plumbing body (with NAC pins) that synonyms 
    it to other low-asserted signals.  (The error complains about
    the synonyming of the high asserted signal to the low asserted
    signals on the level below.) (Both compilers, but more obvious
    with SCALD compiler.)


ValidCOMPILER 1.2l -- Production release on uVAX
SCALD compiler 8.1b

    Killing the page compiler (with control-C) on UNIX platforms can
    result in its getting confused during the next run about what
    needs to be recompiled for the drawing it was compiling when
    killed.  It can also leave an unfinished page expansion file that
    causes the linker to crash.

    Control-L (up-page) in monitor looks bad on PC/AT and VMS.

ValidCOMPILER 1.2m -- Production release S32
SCALD compiler 8.1c

    Global signals synonymed to interface signals within plumbing bodies
    get transformed into local signals within the drawing that used the
    plumbing body.

ValidCOMPILER 1.2n -- Production release PC/AT (OPUS system 5) CANCELLED
SCALD compiler 8.1d

    Random core dumps on PC/AT caused by bug in security software.

ValidCOMPILER 1.2o

    Core dump discovered by QA (exact cause unrecorded).

    Error reporting loses track of the current text macro expansion
    if the error occurs at the end of the text macro definition.
    This results in confusing error messages that specify the
    original string, but do not show how it was text-macro expanded into
    the error condition.  { Fixed only in the ValidCOMPILER }

    Spurious "ERROR(162) Interface and local signals conflict" message
    when interface signal has a local complement.  The error is order
    dependent and does not always occur. { The actual bug was fixed in
    the linker.  This version of ValidPAGECOMP contains a hack that
    prevents the bug from occurring even with an unfixed linker.
    When all tools have been updated with a post-1.1.7 linker, then
    this hack can be removed. }  STARS 559.

1.2p -- Production release PC/AT (OPUS system 5)

    Linker dumps core if ABBREV property is missing from a primitive.
    { Fixed in post-1.1.7 linkers, but this compiler insures that 
    PRIMs and PARTs always have ABBREVs so that the core dump will
    not occur even with the 1.1.6 or 1.1.7 linkers } NOT YET VERIFIED

    ValidCOMPILER issues no error message if a single-versioned
    drawing contains a selection expression in its first page that
    evaluates FALSE.  It also emits no error message for a mismatch
    between the selection expression on a pre-7.0 GED drawing and
    the one in the menu drawing for that version.

    ValidCOMPILER does not correctly handle selection expressions
    in single-versioned primitives -- these must be compiled
    with context so that the selection expression can be evaluated.
    (Normally, single-versioned primitives are assumed to require
    no context, as primitives usually contain little more than
    a drawing body with TITLE and ABBREV properties.)

    Spurious failure of 1.2o to open CMPLOG file on PC/AT.


1.2p VMS (alpha)

    Compiler does not treat master libraries sensibly -- their SCALD
    directory specifications should be relative to the directory (and
    network node) containing the master library.  It should also 
    allow later specifications to override earlier ones, so that
    those in the default master.lib can be overridden by the user.

    { Error(230) 'Trouble with file name manipulation' added
      to this release. }


1.2p-1 VMS (alpha)

    VMS ValidCOMPILER does not work over DECNET.


1.2p-S1 { special release for the Dana Group }

    VMS ValidCOMPILER fails to update modified drawings. (Bug
    introduced in alpha code only.)

    ValidCOMPILER assumes that "current time" on the remote machine 
    containing the drawing being compiled is the same as on the
    local machine.  This is wrong. { VMS version only }

    { Error(230) (introduced for 1.2p VMS) has been deleted in favor
      of a more time-honored message. }

    Having non-contiguous pin (and interface signal) subranges in
    hierarchical drawings causes the interface signal to be used
    as its own base for some bits (rather than the signal connected
    to its pin.  This bug appears only in ValidCOMPILER versions later
    than 1.2m and only in the cmpexp.dat file.
    STARS 741.

    Having a file such as old_extracted_capacitance (with > 15 chars
    after the first '_' and before any '.' ('$' for VMS)) causes
    the compiler (whether ValidPAGECOMP or SCALD Compiler) to dump
    core.
    STARS 722

    Simultaneous ValidPAGECOMP access to drawings (under VMS) causes
    one of the compilations to bomb with "Unable to access schema file"
    error.

    VMS ValidCOMPILER 1.2p-1 fails to update modified drawings. (Bug
    introduced in alpha code only.)

1.2q-Beta1

    { expansion and list file names no longer entered in string table,
      but are now created and released for each page. }

    Copy operations that modify the "last-modified-time" of the intermediate
    expansion files and connectivity files result in random behavior regarding
    whether or not the copied pages will be recompiled.  This has been
    observed when copying drawings on UNIX machines with "cp -r".  
    It would also affect drawings copied with the VMS "copy" command.
    { The new procedure does not check the expansion file time against
    the connectivity
    file time -- instead it checks the connectivity file time against the
    value it had when last compiled.
    If it is different, all prior results for the page are discarded and
    the page is
    recompiled.  The time on the expansion file is not even considered. 
    This scheme also stands up well to time-of-day clock fiddling. }

1.2q-Beta2

    Page compiler does not recompile a page that contains a string
    valued parameter whose value is an (undefined) identifier when
    that identifer later becomes defined as a text macro.

    Page compiler sometimes fails to recompile pages that should
    be recompiled due to changes in text macro definitions.
    (Bug introduced into 1.2q-Beta1.)

1.2q-Beta3 SCALD 8.1g

    If SCALD compiler is given a list of files for the PROPERTY_FILE or
    TEXT_MACRO_FILE directives, it only finds the first one as it
    upshifts the names of the others.
    STARS 768.

    Simultaneous drawing access by page compiler causes collision problems
    (UNIX platforms only).
    STARS 495.

1.3-Alpha1

    { See 1.3 ERS }

    Page compiler can not handle having mode 750 on drawing directory.
    STARS 630.  { Fix peculiar to 1.3, as it is a side effect of shadow
    directories }

1.2q-Beta3 SCALD 8.1g { continued }

    SCALD compiler outputs concatennated constant all on one "logical"
    (with continuation characters) line, though when there are pin
    properties present the line can get very long.  This is a problem
    as the target SCALD applications cannot handle logical lines longer
    than 255 characters.  STARS 517.


1.3-Beta1

    { Random problems observed during alpha test and all the above bugs }


1.2 foo-P1
1.3-Beta1+

    When generating chips files with "compile" elements with NEEDS_NO_SIZE
    TRUE are output with SIZE = '-1' (should be 1).

    { Implemented special analog designer compilation -- when subckt files
      are encountered (while doing this) the compiler generates a primitive
      for the drawing with the property SUBCKT="name of subckt file"
      on it as a drawing property.  Subckt files are called subckt under
      UNIX and SUBCKT.DAT under VMS. 1.3 only }

1.3 foo-b2

    1.3 ValidCOMPILER loses simulator memory primitives -- they are just
    dropped from the expansion file.

    ValidCOMPERR 1.3 reports not finding expansion files for parameterized
    drawings though they were compiled.
    (Makes the error listing useless for dealing with parameterized drawings.)

1.3 foo-B3

    Page compiler goes into infinite loop with extraneous ' at end of
    low asserted signal.  STARS 698. { NOTE: stars 698 actually
    complained about infinite loop from a signal name of the form
    INPUTHIER='IN.  This could not be duplicated.  STARS 382 (listed as a
    duplicate of 698) did complain about the former case which was
    duplicated and verified as fixed. }

    Some error messages involving syntax errors have confusing junk
    preceeding the actual string. { Fixed in ValidCOMPILER only -- this
    was a hangover from the syntax error message fixes that went into 1.2o }

    ValidPAGECOMP does not report error for reversed pin subscripts
    (as obtained by using a step of -1) though they are illegal.
    Example: A pin named A<0..3:-1> is illegal in format 1.
    { The error message 218 has been changed to reflect its full
      meaning -- it now says "Pin subscript must be a simple subrange"
      rather than "Bit lists are not permitted in pin names". }

    VAX comperr unable to open CmpLst file.  { Bug introduced in 1.3 }

    Directory name chosen for default shadow directory can be duplicated
    under some conditions, resulting in a subsequent assertion check
    violation "YEOWW!!" from the compiler with core dump.
    { introduced in 1.3 }

    If ValidSIM is run and there are no compiler errors, then if there
    was a cmplst.dat laying around from some other compilation, it will
    still be there -- this is confusing.  The same is true for other
    ValidTOOLs other than ValidCOMPILER. { The page compiler now always
    deletes this file .}

    If the SHADOW_ROOT directive is specified, the specified directory
    may not be created with permissions set as specified by the SHAREABLE
    directive.

1.3 foo-B4

    Range check error when property values are encountered that end with
    the character '%'.
    
    Segmentation violation in page compiler when using analog designer with
    subckt files. { compiler understanding of these is a new feature of 1.3 }

    { MERGE_DRAWINGS directive default value has been changed to ON.  This
      effectively deletes the language change of ignoring all but one
      drawing directory existing for a given drawing.  The compiler will
      treat this case as it has before (for non-ERROR) conditions.  Note
      that it is no longer necessary to document this directive . }
      

1.3 foo-B5

    { Changes to debug_23 }

    When certain fatal errors occur (such as plumbing drawing not found)
    the page is compiled twice.

    When certain fatal errors occur (such as plumbing drawing not found)
    comperr will erroneously report the the page was not compiled (thus
    preventing the real error(s) from appearing in cmplst.dat).

    The SCALD compiler reports message 107 as an ERROR when it should
    be a WARNING.

    ValidLINKER reports ABBREV conflict oversight for drawings with 
    pages that can be (and are) selected out for certain contexts
    through the use of selection expressions.

1.3 foo-B6

    { Changed comperr script to go with linker fix to automatic 
    compiler mechanism -- the use of 1.3 foo-B6 linker REQUIRES
    the script, but the script is compatible with older linkers and
    compilers, so the script can be liberally distributed. }

    If a text macro has a parameter whose value is also a text macro that
    ends in a non-letter, the compiler does not expand the parameter.  Ex.
.nf
    with text macro definitions
        FOO2 = '2';
	BAR = 'XYZ %1'
    used in a parameter value as DELAY='BAR FOO2', the result is
        DELAY='XYZ FOO2';
    instead of the correct 
        DELAY='XYZ 2';
.fi

    If a text macro parameter is used more than once in the definition
    of a text macro, the compiler substitues a null value for all
    usages after the first.  Ex. 
.nf
    if text macro definitions
       BAR = '%1*%1';
       FOO = 2;
    are used in DELAY='BAR FOO', the result will be
        DELAY='2*';
    instead of the correct
        DELAY='2*2';
.fi

    Text macros occurring in non-integer parameter values are not getting
    expanded unless they occur at the very start of the value.


1.3 foo-P1

    If errors occur in a SCALD directory, only the first such error
    will be reported.

1.3 foo-P3

    REPORT_HIERARCHY is not implemented by ValidCOMPILER.

    ERROR_HELP ON is not implemented by ValidCOMPILER.

1.3 CMS-P4 { released before other platforms, so has only some of the fixes }

    A bogus error 177 is issued when a connectivity file cannot be read
    (error 205).

    CMS version exceeds record length limit in CMPLST and CMPLOG when
    parse errors are emitted and the file being parsed is of fixed length
    format.

1.3 foo-P4   -- production release, VAX, SUN

    ValidLINKER dumps core if user specifies a signal name that begins with
    a left parenthesis.  { This is now caught by the compiler and
    flagged as an error -- it should never have been allowed as it
    leads to confusion over whether the signal has a path name once
    it gets to the compiler output. }

    If a shadow directory is specified in a LIBRARY directive, the
    compiler erroneously upshifts its name.  { Affects UNIX systems
    only. }

    An assertion failure message is issued by the compiler when
    signal scope conflicts occur.

    SCALD compiler emits bogus error when SHAREABLE directive is used.

1.3-P5 -- production release PC/AT and S32

    Psuedo-EFS access does not work.

1.3-S1

    Error 252 is not documented in cmperrors.mem.

    { Error 60 "Same shadow directory used more than once" has been added. }

    When the user specifies the same shadow directory for more than one
    SCALD directory (or library), the compiler emits an assertion check error
    with a cryptic message.

    Compiler fails to determine signal width when 10 synonym bodies are
    connected in series.
    STARS 1209.
    {Internal NOTE: iteration safety limit on width resolution was bumped to
     500. Same goes for the iteration limits on assertion resolution and
     base signal resolution.  The latter was previously at 150, the other
     2 were at 10. }

    When the page compiler encounters a PRIM or PART drawing that has only one
    version but with a selection expression on it, it tells the linker to
    read a non-existent file on the first run.  (The linker then dumps
    core.)  Subsequent runs work ok.
    
    Compilers (compile and compile -o) incorrectly handle NWC 
    pass-through pins on hierarchical plumbing bodies when connected to
    an NC signal.

1.3-S2

    Compiler does not correctly interpret the replication property on an
    NC signal. If a replicated NC is synonymed to some other (non-NC) bus,
    it synonyms together the bits of the bus.  (Hindsight note: This bug
    existed prior to 1.3 SUN-S1, but
    could have occurred only under VERY rare circumstances.  The changes
    made for that release to fix the handling of NCs connected to
    hierarchical NWC pins brought it out into the open.)

1.3-P6

    A page has signal a<0>\i and -a<0>\i entering the same 2 merge which
    connects to an unbubbled pin.  The compiler complains about
    "synonyms must use same assertion" (when they do).

    { Iteration limits bumped in SCALD compiler to match those in page
      compiler (see STARS 1209 above for 1.3-S1) }

    Message for error 218 issued by SCALD compiler does not match that
    issued by ValidCOMPILER.

    { Noticed a small bug in comp -- in readged.pas there are debug_20
      statements that always print to CMPLST without checking to see
      if it has been opened. -- fix for some later release. ALSO -- fix
      up the case statement for the debug directive (both compilers) so
      that it has an "otherwise" to handle out-of-range stuff. }

    CLOCK_DELAY property (for timing verifier) is omitted from property.dat.
    STARS 974.

1.3 VAX-P6

    Core dump when debug 24 is used -- internal only.

    Elapsed time reported by ValidCOMPILER (expgen) for directives file
    reading is incorrect. (Wildly so for the VAX, but seems close to
    reasonable for SUN and S32.)

1.3 PC-P7

    { Modified to work under the Valid 3.0 OS w/ NFS.  Note that this
    code will no longer work for the old OS. }

1.3 VAX-S3

    ValidCOMPILER does not run on the CVAX due to runtime library
    incompatibility.  

    { Released using shared libs -- only for DAC }

1.3 VAX-P7

    { released with ValidLINKER 1.3-P2 }

    Sharing shadow directories on the VAX does not work -- directory creation
    fails if one user is creating a directory within another user's directory
    (even though he has write/execute permission on the other's directory).

1.3 SUN4-A1

    Pascal runtime error "non-positive format width: 0" occurs for
    SCALD compiler (compile -o).   Does not happen for page compiler.
    (Workaround -- turn path name reporting off using the
    REPORT -PATH_NAMES; directive.)
    { in print_string_formatted }

    When Error 247 occurs due to FLAG body having a logic drawing in
    2 libraries, the compiler does not recompile that page containing
    the FLAG body when the error is fixed by deleting the logic
    drawing from the sim library.  This leaves the error in the list
    file.

???

    When error 247 (pages of version across SCALD directories) occurs,
    the page compiler ignores the wrong one -- it should use the
    last one specified, but with directories overriding libraries.

    Suppress 245 does not work.

    The description of OVERSIGHT 249 in the cmperrors.mem file is munged.

1.3 SUN4-P6

    { Released with 1.3-P6 ValidLINKER }

1.3-S4

    Primitives that contain text-macro invocations dependent on parameterization
    are not correctly handled unless an EXPR property is present.  (Workaround
    is to put EXPR=TRUE on the drawing body.)

    ValidCOMPILER does not run on CVAX due to changes to VAXC/VMS interface.

    Page compiler will occassionaly mangle the name of a SCALD directory
    and then complain about not finding it.  { UNIX only. }

    Linker generates assertion check failure "Page already exists" and
    then exits when compiler compiles a drawing with many (and/or long-valued)
    parameters. (That is, that parameter names and values concatenated 
    together produces a long string.)

1.3 VAX-P7

    This version has been generated to run on the CVAX.  The previous version
    did not run on this platform due to runtime library incompatibility.
    It is expected that this version will run on all VAX platforms currently
    supported by Valid.

1.3 VAX-P8

    This version is identical to version \*(OV except that it has been
    linked with a revised version of the security libraries in order to
    be compatible with VMS 5.0.  (This should not affect its behaviour under
    VMS 4.x.)

1.4-B1

    { Page compiler no longer checks for error 177 (excepting plumbing bodies)
      -- this can ONLY occur on drawings that use MENUs (which are long 
      obsolete). }

1.4-B2

    Can't turn off creation of cmpexp.dat with OUTPUT directive.
    STARS 1564.

    Infinite loop in SCALD compiler ERROR_HELP processing.  STARS 1659.

1.4-B3

    OVERSIGHT 176 not documented in ERROR_HELP output.  STARS 1820.

    Compiler issues no error when SIG_NAME is improperly connected to
    something by the user.  STARS 1866.

    Compiler doesn't report pin that's a subrange of another pin as
    an error -- linker then dumps core.  STARS 1780.
    
1.4-P1


1.4-P2(?)

    ERROR(253) is emitted incorrectly when an ill-formed cardinal bit tap
    is encountered.  The correct error to emit is ERROR(69).

    ValidCOMPILER does not properly handle PRIMs with context sensitivity
    (such as selection expressions).   Alternate compilations yield correct 
    results.   STARS 1958.

    Assertion check violation 154 occurs when an identifier is defined as both
    a parameter and a local text macro for the same drawing.  NOTE: this has
    been fixed so that the parameter definition overrides the local text macro.
    This allows local text macros to be used to define default values for
    parameters on a drawing-by-drawing basis.

    Drawing contains PART.1.1, SIM.1.1 and SIM.2.1.  When compiling for logic,
    page compiler quits with message "menu version isn't first in list".
    STARS 26852.

1.4-S1

    { Loaded with linker 1.4-S4.  Fixes bugs fixed therein. }


    