I'm evaluating Zeus for a Borland Pascal 7 project. I'm trying to get rid of Multi-Edit.
Stuff is working OK but I don't speak"regular expression".
Compiler errors look like this --> NEXTHERM.PAS(8)
NEXTHERM.PAS(26): Error 3: Unknown identifier.
The error is on line 28 above. Can you help me with regular expressions to make Zeus jump right to the file and goto the line number automatically?
Thanks,
Tim
Borland pascal regular Expression
Are you sure Zeus the built-in regular expressions are not already doing what is required 
I ran a test using the error details you provided and as far as I can tell the default regular expressions detected this line of output output:
I think all you need todo is make sure the pascal compiler command line is correctly defined for the pascal document type and you should be away
For more details on this is done refer to the Configuring Zeus to Run a Third Party Compiler help topic.
Cheers Jussi
I ran a test using the error details you provided and as far as I can tell the default regular expressions detected this line of output output:
as an error, detect the file as NEXTHERM.PAS and detected the line number of the error as 26.NEXTHERM.PAS(26): Error 3: Unknown identifier.
I think all you need todo is make sure the pascal compiler command line is correctly defined for the pascal document type and you should be away
For more details on this is done refer to the Configuring Zeus to Run a Third Party Compiler help topic.
Cheers Jussi
-
Guest
Borland Pascal regular expresions
Hi,
Thanks for your very informative reply. I have followed the instructions and am still getting the same result. That is the error line is a different color; double clicking on the error takes me to the file with the error; but not to the error line. Double clicking takes me to the top of the file and I have to scroll to the error.
The pertinent regex lines are currently blank - so the editior's default search terms are not working for me. Can you provide regex strings I can try? I don't speak regex yet and examples will help me get the hang of it.
Secondly - is there a way to make the editor jump to the error automatically?
I have another question but I'll start another thread.
Thanks,
Tim
Thanks for your very informative reply. I have followed the instructions and am still getting the same result. That is the error line is a different color; double clicking on the error takes me to the file with the error; but not to the error line. Double clicking takes me to the top of the file and I have to scroll to the error.
The pertinent regex lines are currently blank - so the editior's default search terms are not working for me. Can you provide regex strings I can try? I don't speak regex yet and examples will help me get the hang of it.
Secondly - is there a way to make the editor jump to the error automatically?
I have another question but I'll start another thread.
Thanks,
Tim
Hi Tim,
This is a good start as it does means the line is at least being identified as a line of error
Also use the Workspace, Options menu to check the General section of the Workspace, making sure a Line regex has not been defined for any currently open workspace, or the default workspace. Both of these should be blank.
But you do have the choice of configuring if/when the error window is display/not displayed, using the Compiler section of the document type.
Thus if you configure the window to never display. Then when you run the compile, and indication of errors will be displayed in the status bar and you can then use the next/previous error buttons found on the toolbar to navigate the cursor to the first/next/previous errors.
Naturally you can also configure the next/previous error buttons to work of a keyboard key combination.
So the navigation is not automtic but it is almost semi-automatic
Cheers Jussi
That is the error line is a different color; double clicking on the error takes me to the file with the error;
This is a good start as it does means the line is at least being identified as a line of error
This is a bit strange as I am not sure why it is not working, but in any case it should be easy enough to fix. Try doing the following:but not to the error line. Double clicking takes me to the top of the file and I have to scroll to the error.
- Open a pascal file
- Use the Options, Properties menu to bring up the document type for that file.
- You should get the document type dialog and the caption of the dialog should indicate that you are editing the pascal document type.
- In the Line Regex field of the General section enter \([0-9]+\) as the regular expression.
- Apply the changes and try to run the compile again.
Also use the Workspace, Options menu to check the General section of the Workspace, making sure a Line regex has not been defined for any currently open workspace, or the default workspace. Both of these should be blank.
Unfortunately I don't think this is possibleSecondly - is there a way to make the editor jump to the error automatically?
But you do have the choice of configuring if/when the error window is display/not displayed, using the Compiler section of the document type.
Thus if you configure the window to never display. Then when you run the compile, and indication of errors will be displayed in the status bar and you can then use the next/previous error buttons found on the toolbar to navigate the cursor to the first/next/previous errors.
Naturally you can also configure the next/previous error buttons to work of a keyboard key combination.
So the navigation is not automtic but it is almost semi-automatic
Cheers Jussi
-
Guest
Borland pascal regular Expression
Hi,
This seemed to be working after I installed the purchased version yesterday. But this morning it is working incorrectly again as I described. Double clicking on the error jumps to the correct file but not to the line. Actually - it worked corectly the first time I tried it, then quit working after I experimented with the $FB$EXT macro tags you suggested in another post. The macro tag worked well though. I added the sugested regex to the General/Line section but there was no change.
I'm puzzled.
This seemed to be working after I installed the purchased version yesterday. But this morning it is working incorrectly again as I described. Double clicking on the error jumps to the correct file but not to the line. Actually - it worked corectly the first time I tried it, then quit working after I experimented with the $FB$EXT macro tags you suggested in another post. The macro tag worked well though. I added the sugested regex to the General/Line section but there was no change.
I'm puzzled.