ErrorLogParsers is a package for routines that parse compiler error messages. So far it contains only one module, CycleThruErrorLog, which registers a parser using FileViewerOpsBackdoor.RegisterErrorLogProc.

CycleThruErrorLog puts an errlog button in the viewer of a source file. This button can be used to move sequentially through the errors listed in the associated errlog file. (There must be a file foo.errlog for the source file foo.mesa.) The first click on this button will open the errlog file. Subsequent clicks will move among the errors listed in the errlog, scrolling both the source file and the errlog file as needed. Edits to the source file are correctly accounted for, so that moving to subsequent errors will show the correct places in each file.

You must set Compiler.ViewSeparateLogs: FALSE in your user profile.

In Cedar10.1 the compiler would automatically put an errlog button in the viewer for a source file that had an error in it. Similarly, when a source file had been successfully compiled, the compiler would remove the errlog button and close any .errlog file that had a viewer open on it.

In PCedar2.0 this automatic management of the errlog button and errlog file is not available. (Most people run their language tools in a separate PCedar world.) To "activate" the errlog button for a source file, you must instead invoke the command

This command will put an errlog button in the viewer for the file filename.mesa.

NOTE: Unlike DCedar, you do not need to invoke CycleThruErrorLog anywhere. The ActivateErrorLog command will do all the necessary initialization.

One good way to invoke this command is to add a button to your command viewer that will invoke it for a selected filename. (The compiler prints out the names of all files for which it finds errors.) To get such a button, put something like the following line in your CommandTool.PerCommandTool entry in your user profile:

The following actions can be invoked through the errlog button: