I know this forums isn't really for Turbo Pascal, but Delphi is based off of Turbo Pascal.
I'm doing a research paper on the Turbo Pascal programming language. I need to make points on concurrency and exception handling in the language, even if the language does not support it. Does Turbo Pascal support either of these? I don't think it supports exception handling, but I am having a hard time finding information on either topic. Does anyone have any websites that I can use to cite as a source?
Thanks
Turbo Pascal 5.5 supported some OO programming, but not exceptions really IIRC. This is a feature list for Turbo Pascal 5.5
http://community.borland.com/article/0,1410,20803,00.html
Turbo Pascal 7.0 was replaced by Delphi 1, which has exceptions. Don't know if TP7 had any though.
I think exception handling first came with Delphi 2 which was the first 32bit Windows pascal from Borland. Delphi 1 was designed for the Windows 3.1 16bit enviroment. Runtime error's 216 (UAE) where very common when you develop with Delphi 1.
With Turbo Pascal for DOS you was able to install an error Handler for catching runtime error's. There was an error variable (IOResult?) for handling I/O-errors such as "File not existst"...
Yes, it exists.
if IOResult<>0 then
//you obviously tripped a file error somewhere....
I know its C style comments, but FPC allows them.As yes, its a delphi clone.I don't know what you're talking about.Maybe delphi didn't support this.FPC always has.TP always has.
there is another in which you seek similar to procedure ExceptionDivideByZero; interrupt; or similar.Im looking for that too.
If Pascal didnt have interrupts or IOResult, how can I write or contribute to an OS WRITTEN with it,FPC namely, [and WITHOUT and BEFORE delphi objects were added in mind you.....] at all and get the kernel to avoid tripping them???
you are not making any sense.
you cannot both program an interrupt, use an interrupt (or exception) and say they dont exist.
the try...finally and try...except came about because of python's C-style error handling, YES, with EXCEPTIONS, but it wasn't implemented like the code above.You had to manually check and poll EVERY time back then.