• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

antlr/22-Nov-2023-38,54931,213

dlg/22-Nov-2023-7,0545,540

h/22-Nov-2023-8,5085,725

support/22-Nov-2023-3,8993,032

CHANGES_FROM_131.txtD22-Nov-202316.2 KiB523375

CHANGES_FROM_133.txtD22-Nov-202388.6 KiB2,4491,674

CHANGES_FROM_133_BEFORE_MR13.txtD22-Nov-2023140.4 KiB3,6672,634

CHANGES_SUMMARY.txtD22-Nov-202380.6 KiB2,0501,537

KNOWN_PROBLEMS.txtD22-Nov-20237.6 KiB242165

MPW_Read_MeD22-Nov-2023524 2215

MakefileD22-Nov-2023471 169

NOTES.bccD22-Nov-20235.3 KiB185141

NOTES.msvcD22-Nov-20237.1 KiB190144

READMED22-Nov-20235 KiB160109

RIGHTSD22-Nov-20231.1 KiB2722

history.psD22-Nov-202319.8 KiB

history.txtD22-Nov-20238.4 KiB187124

makefile.oldD22-Nov-20231.9 KiB6745

README

1
2                          Parr Research Corporation
3                                    with
4                  Purdue University Electrical Engineering
5                                    and
6                       University of Minnesota, AHPCRC
7
8                                Terence Parr
9                                Russell Quong
10                                 Will Cohen
11                                 Hank Dietz
12
13
14A central place for information about PCCTS 1.33 is:
15
16        http://www.polhode.com/pccts.html
17
18The maintenance release is available from:
19
20        http://www.polhode.com/pccts133mr.zip
21
22There is a ready-to-run version for win32 for Microsoft Visual Studio
23at the same site.  It is available from:
24
25        http://www.polhode.com/win32.zip
26
27New users should visit http://www.polhode.com/pccts.html in
28order to get the following document:
29
30        "Notes For New Users of PCCTS"
31
32This is a Postscript file of about 40 pages which is extremely
33useful for someone starting out. It is a based on 1.33mr21
34
35When you have a little more experience, be sure to review the
36following documents in the distribution kit:
37
38            CHANGES_FROM_133.txt
39            CHANGES_FROM_133_BEFORE_MR13.txt
40            KNOWN_PROBLEMS.txt
41
42-------------------------------------------------------------------------
43                      INSTALLATION (Unix)
44-------------------------------------------------------------------------
450. Download http://www.polhode.com/pccts133mr.zip
46
471. Unzip the distribution kit to your preferred location.
48   If there are newline problems try using zip -a ...
49
502. cd to the main pccts directory.
51
523. make
53
54   This will create:
55
56        antlr
57        dlg
58        sorcerer
59        genmk
60
614. Copy to /usr/local/bin or /usr/local/bin if you like.  If you
62   don't wish to then add pccts/bin to your path.
63
645. To get an up-to-date list of program options execute the
65   program with no command line options.  To get up-to-date
66   documentation read CHANGES_FROM_133*.txt and KNOWN_PROBLEMS.txt
67   at:
68
69           http://www.polhode.com/pccts.html
70
716. You need not create a library.  The makefile created by genmk
72   assumes that the files are not part of a library.
73
74   If you wish to create a library from elements of pccts/h:
75
76   If the first letter of the filename is lowercase (uppercase) it is
77   related to the code generated using the pccts C mode (C++ mode).
78   Some of the .c and .cpp files in the h directory are not meant to
79   be placed in a library and will not compile because they are meant
80   to be #include in pccts generated files which are grammar specific.
81
82   For C++ users place the following elements in the library:
83
84        AParser.cpp
85        ASTBase.cpp
86        ATokenBuffer.cpp
87        BufFileInput.cpp (optional)
88        DLexerBase.cpp
89        PCCTSAST.cpp
90        SList.cpp
91
92-------------------------------------------------------------------------
93                    INSTALLATION (Win32)
94-------------------------------------------------------------------------
95
96I've tried to keep the win32 kit to the minimum necessary to get
97up and running.  The complete kit contains additional information
98(some historical), source code, and DevStudio projects for
99rebuilding pccts from the source code.
100
101The kit is now distributed with both MSVC 5 and MSVC6 style projects.
102
1030. Download http://www.polhode.com/win32.zip.
104
105   You may also wish to download:
106
107        http://www.polhode.com/CHANGES_FROM_133.txt
108        http://www.polhode.com/CHANGES_FROM_133_BEFORE_MR13.txt
109        http://www.polhode.com/KNOWN_PROBLEMS.txt
110
1111. Unzip the distribution kit to your preferred location.
112
113   This will create:
114
115         a pccts directory tree
116            pccts/bin/*.exe
117            pccts/lib/*.lib
118            pccts/h/*
119            sorcerer/lib/*
120            sorcerer/h/*
121
122         an example directory tree
123            pccts\example\calcAST\*
124            pccts\example\simple\*
125
1262. Define the environment variable PCCTS to point to the main
127   pccts directory.
128
1293. Try building the simple project: pccts\example\simple\simple50.dsw
130   or simple60.dsw.
131
1324. Try building the complex project: pccts\example\calcAST\calcAST50.dsw
133   or calcAST60.dsw.
134
135-------------------------------------------------------------------------
136                      INSTALLATION (DEC/VMS)
137-------------------------------------------------------------------------
138
139DEC/VMS support added by Pi�ronne Jean-Fran�ois (jfp@altavista.net)
140
1410. Download http://www.polhode.com/pccts133mr.zip
142
1431. Unzip the distribution kit to your preferred location.
144
1452. set default to the main pccts directory.
146
1473. @makefile.vms
148
149   This will create in directory [.bin]:
150
151        antlr.exe
152        dlg.exe
153        sorcerer.exe
154        genmk.exe
155
1565. To get an up-to-date list of program options execute the
157   program with no command line options.  To get up-to-date
158   documentation read CHANGES_FROM_133*.txt and KNOWN_PROBLEMS.txt
159   at http://www.polhode.com/pccts.html.
160