Parser Generator

Parser Generator

Release Notes

24

th

November, 2003

Version 0.11

1) The Output window has now gained its own pop up menu when the right mouse button is pressed.

Admittedly the pop up is not very big.

2) The operation of the right mouse button has been improved slightly. If the cursor is placed over a

Note that if only AYACC options are changed then only YACC files will be built. Correspondingly,

the same also applies to Lex files.

6) The cursor in the editor windows, including the Output window is now moved correctly when the

window is scrolled.

7) Code generated by AYACC can now be compiled with Visual C++ version 1.52c. The problem

occurred when the -d option (define header file) was used. The #endif at the end of the file did not

have a trailing newline.

8) Another problem related to the -d option was the file name in the #ifndef statement generated at the

top of the file. This has now been shortened to just the base name plus extension. Note that the dot is

replaced with an underscore.

Error commands.

2) It is now possible to compile files where there are spaces in the full path name of the file.

3) The New Project dialog box can also handle spaces in the project path name. It will also prompt you

to create any directories that do not exist.

Version 0.13

1) Very simple grammars along the lines of:

a: ‘A’;

Would cause Parser Generator to output a C file, which could not subsequently be compiled. The

problem was caused by an un-initialised array.

2) The Window menu has been revised. It now has both a Tile Horizontally and Tile Vertically

6) A Save All, Undo, Redo and Stop Build button have been added to the tool bar.

7) The Status bar has been revised slightly.

8) Help files have been modified. They are still not finished.

9) File drag and drop is now supported. Note that this is not to be confused with the other more

generalised form of drag and drop. File drag and drop is where you drag a file from somewhere, i.e.

Windows Explorer, and drop it in an application, in this case Parser Generator.

10) When compiling a file you can now continue to interact with Parser Generator. Before Parser

Generator would appear to lock up. Note that this was not particularly noticeable if you were

compiling small source files.

11) The editor now supports splitter windows. You can have a maximum of 4 separate views in one

would not re-appear when the mouse was moved.

15) The Editor Options dialog box has gained two more options. One controls whether you want the view

to redraw when you are dragging the scroll box in a scroll bar. The other controls whether you want

to be prompted when automatically loading externally modified files.

Version 0.14

1) Corrections made to the project rebuild mechanism again. The previous implementation was not

quite right.

2) The setup program now registers the “.pgp” extension as a Parser Generator Project in the Registry.

You can now open Parser Generator projects from Windows Explorer by double clicking the icon.

Version 0.15

NT machines only.

selected completely. This has now been corrected.

6) There were a number of bugs to do with the handling of errors in the Output window. These related

to modification of the source files containing the errors, scrolling of the windows, closing of source

windows etc. In other words there were quite a few. These should now all be fixed.

7) The editor should now be able to deal with foreign keyboards. In particular this relates to accents

over characters. For instance an umlaut over an o.

8) There were a number of minor problems with the display of information in the Status bar. This

included the READ pane not displaying the text when a read-only file was opened, and the line

number and column panes showing 00000 and 000 respectively when a dialog box (i.e. the Line

dialog box) was displayed.

9) The editor now handles the overwrite mode correctly. Before it treated both the insert and overwrite

been corrected.

what was selected a tab would always be inserted. This has now been corrected.

12) When more than one line is selected, pressing the tab key will now cause the selected lines (except

the last one) to be indented. Note that if the shift key is held down, then the selected lines are un-

indented. An indent is assumed to be one tab stop in width.

Version 0.16

1) The Tools menu is disabled (greyed) if there are no menu items in it.

2) There was an occasional divide by zero error when an editor window was opened. This was

introduced in version 0.15. This has now been corrected.

3) The macro parsing for tool arguments has been improved. It is no longer bothered with any trailing

characters after the macro. Before they had to be a non-alphabetic.

4) The start state <*> at the front of a regular expression in ALex is now recognised. This is really just

resultant grammar used by ALex is:

< start-list >

< * >

7) Compound statements can now be nested in {…} actions in ALex and AYACC, i.e. {…{…}…}.

8) If a % sign were embedded in %{…%} in ALex then it would cause a fatal-error. This has now been

corrected.

9) It is now possible to have more than one start state at the front of a regular expression in ALex, i.e.

<AA,BB>. Before it would have caused a syntax error.

10) The contents of the Find What box in the Find/Replace dialog boxes was not always filled out

correctly when the corresponding dialog box was displayed.

11) Character strings in Lex regular expressions were not being correctly syntax coloured by the editor.

This has now been corrected.

12) Embedded actions in AYACC rules were not working correctly. This applied to both the generated

verbose file is now “y_output”. These options used to generate the file “y_output.v”. Note the .v

extension.

2) The %{…%} sequence is now accepted by the AYACC parser when it is placed after the first %%

mark. That is in the rules section. Note that the enclosed code is placed at the top of the parser

action function. This code will be run for every action that is executed. This is in contrast to YACC,

when the code is placed at the top of yyparse function.

3) The %a, %e, %k, %n, %o, and %p internal array size declarations have now been implemented in

ALex. Note that these have no effect on how ALex operates. They are solely there for portability

purposes. The resultant syntax that is recognised by ALex is:

array-decl:

array-keyword:

%option [option-list]

option-list:

option-list identifier

identifier

5) The Save All command in the File menu no longer displays a dialog box every time it wants to save

a file. It only displays a File Save As dialog box when you have modified a file that does not yet

have a file name associated with it.

6) The %a, %e, %k, %n, %o, %p and %option ALex keywords are now syntax coloured by the editor.

7) ALex hexadecimal and octal integer constants are now syntax coloured correctly by the editor

8) For compatibility, new definitions of yyerrok and yyclearin have been added to the AYACC header

11) Code enclosed in %{…%} in both AYACC and ALex can now handle both line //… and block /*…

*/ comments, character constants ‘…’ and string constants “…”safely. That is, it is possible to

include %} character sequences in them.

12) Union code in AYACC can now handle nested { and } characters. These characters can also be

included safely in both line //… and block /*…*/ comments, character constants ‘…’ and string

constants “…”.

13) Syntax colouring for YACC and Lex now takes into account { and } character nesting, line //… and

block /*…*/ comments, character constants ‘…’ and string constants “…” in actions, union code and

%{…%} delimited code.

14) The ALex generated lexical analyser now has growable text (with accompanying state) and unput