26 Apr
2016
26 Apr
'16
6:42 a.m.
On Mon, 25 Apr 2016, Jon Elson wrote:
On 04/25/2016 12:42 PM, geneb wrote:
It's possible. FPC uses GDB for the debugger - you'd have to check to see
if the text mode IDE has the error location feature that the Turbo Pascal
IDE had. I'm not sure about Lazarus as I don't use it often.
g.
--
Proud owner of F-15C 80-0007
http://www.f15sim.com - The only one of its kind.
http://www.diy-cockpits.org/coll - Go Collimated or Go Home.
Some people collect things for a hobby. Geeks collect hobbies.
ScarletDME - The red hot Data Management Environment
A Multi-Value database for the masses, not the classes.
http://scarlet.deltasoft.com - Get it _today_!
On Mon, 25 Apr 2016, Chuck Guzis wrote:
Yes, does that work with FPC on Linux?
On 04/25/2016 09:39 AM, Jon Elson wrote:
Well keep in mind that given that error, you could stick that address into
the "Find Error Location" of the IDE and it would drop you right on the
line of code that triggered the error.
I used it to port a couple of my programs from
(Ughhh!) Borland
Turbo Pascal for Windows to Linux, and it was a surprisingly painless
job. The only thing I notice is the error messages look exactly like
Borland error messages on DOS. (Error 132 at 1B7F sort of thing.)
Historically, one of my pet peeves with compiler writers. IBM 704
FORTRAN had better and clearer diagnostics than many of today's compilers.