Annotation of 43BSD/ucb/pascal/eyacc/READ_ME, revision 1.1

1.1     ! root        1: Copyright (c) 1980 Regents of the University of California.
        !             2: All rights reserved.  The Berkeley software License Agreement
        !             3: specifies the terms and conditions for redistribution.
        !             4: 
        !             5: @(#)READ_ME    5.1 (Berkeley) 4/29/85
        !             6: 
        !             7: August 28, 1977
        !             8: 
        !             9: This directory contains source for a version of yacc needed by the Pascal
        !            10: parser.  The differences between this yacc and a stadard version 6 yacc
        !            11: are indicated in a comment in y1.c.
        !            12: 
        !            13: Note that the standard yacc parser will not work on the tables produced
        !            14: by "eyacc" and also that these changes are really useful only with
        !            15: a fairly large set of error recovery routines which are part of both
        !            16: "pi" and "pxp".  The routines are language independent, but the method
        !            17: will only work on languages which have some redundancy in them... it is
        !            18: probably ill suited for C, but would work fine in ALGOL-60, ALGOL-W,
        !            19: EUCLID, LIS, SP/K, PL/1, ALPHARD, CLU, ...
        !            20: 
        !            21: Sun Apr  8 21:43:08 PST 1979
        !            22: 
        !            23: A paper describing the method used by eyacc will appear in August in the
        !            24: SIGPLAN Boulder conference.
        !            25: 
        !            26: Mon May 5, 1980
        !            27: 
        !            28: The eyacc in this directory has been modified to work for
        !            29: version 7.  This involved syntax fixes and changing the I/O calls
        !            30: to standard version 7 calls.

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.