Hello PHIL!

Replying to a message of PHIL PATTENGALE to ALL:

 PP> I've setup the Speed Pascal v1.5 gamma 1 program and am working thru
 PP> it's English/German docs.  The following code snippet results in the
 PP> following popup error message:

 PP>          Exception Occured

 PP>          Exception occured: Input/Output
 PP>          error (ElnOutError) at $0001041F

 PP>          Program is terminated.

[Code deleted]

 PP> I believe the line marked with the "*" is the one that blows up.
I believe that if the error is near that point, it will be the next line,
as that is where the operating system will be looking for the file (and
thus the line that could cause an I/O error).

 PP> Any ideas anyone?  The core help files (all the function references,
 PP> etc) are in German, although the basic help portions are in English.
 PP> Thus, I'm confused.
Well, you could try having writeln's after every major operation. Then if
the program traps, you know between which lines it occured. You can then
start narrowing down to one line. When you know the line, then you can
probably start finding out the values of the different variables that are
used in that line. Knowing which value is wrong, you can start monitoring
the different values of that variable during the execution of your app.

 PP> I'm trying to read thru the explore.ori (copy of original explore.ini)
 PP> and write to a new explore.ini.  As far as the code is now, I just
 PP> want to clone the top portions of the .ini file and when I reach the
 PP> quicklist section will sort it.
But since I don't have your explore.ini, I cannot test your program. If you
want me to do so, Send me your explore.ini and resend the code to my
netmail number (or e-mail number, if you have e-mail access)

 PP> I presume I am missing some error checking for the file accessing, but
 PP> the program works up just past the rename command (it does rename the
 PP> file).
No, you have errorchecking for the file turned on, since you would not get
such a nice dialogbox if you hadn't: the compiler runtime library would not
know the error occurred.

 PP> Has v1.5 been released yet?  The docs alone would be worth the $$$
Yes, it has. (The demo at least, I suppose the final program is there
directly after the demo)

 PP> Thanks!
Welcome..
 PP> Phil

Bye, Erik!
[TeamOS/2 NL]
reactions preferrably by echomail
_personal_ reactions preferrably by e-mail
[internet: ErikH{at}hcc-gron.idn.nl]

--- FleetStreet 1.14 NR