Hi George
There is an error in the Turbo parser at line 14490. Here is this line:
14490 IF var%0
AND (struct%(var%)directive_mask%)=directive_mask%
Both sides of the AND get to be evaluated. Although var% is tested for being
non
negative on the left hand side, the right hand side will
Hi Michael
On 22 Feb 2012, at 13:31, Michael Bulford wrote:
There is an error in the Turbo parser at line 14490. Here is this line:
14490 IF var%0
AND (struct%(var%)directive_mask%)=directive_mask%
Both sides of the AND get to be evaluated. Although var% is tested for
being non
Hi George
On Wednesday, 22 February 2012, 14:24 George Gwilt wrote:
You are quite right. But how did you get var%=-3? Does this imply another
mistake in Parser?
No, I don't think so. -3 comes from for_flag% for an earlier occurence of p
Your solution looks the best - it's neater.
In message 1329917514.17351.yahoomail...@web171518.mail.ir2.yahoo.com,
Michael Bulford michaelbulf...@yahoo.co.uk writes
Hi George
There is an error in the Turbo parser at line 14490. Here is this line:
14490 IF var%0
AND (struct%(var%)directive_mask%)=directive_mask%
Both sides of
On 19 Feb 2012, at 15:07, George Gwilt wrote:
I use DEBUG 0 and 1 for the same reasons as you and have never had the fault
you mention.
If you could send me, privately, a copy of your program I'll try to locate
the problem.
Thanks for your offer of help, this is really
Hi Michael
On 21 Feb 2012, at 11:16, Michael Bulford wrote:
I have a copy of parser506_bas and have managed to compile this
with line numbers included. Trying this
on my program the parser stops at line 14490, which is in the middle of
ignoring
code. I then inserted the following line
On 18 Feb 2012, at 13:38, Michael Bulford wrote:
I use DEBUG 0 and 1 for the same reasons as you and have never had the fault
you mention.
If you could send me, privately, a copy of your program I'll try to locate
the problem.
Thanks for your offer of help, this is really
Hi Michael
On 17 Feb 2012, at 19:25, Michael Bulford wrote:
There is some code in my program that I do not want compiled: this is only
used when the SuperBASIC version is running. So, I use DEBUG 1 before the
code and DEBUG 0 afterwards. When compiling the parser stops with the report
Hi George
On Saturday 18 February 2012, 9:56George Gwilt wrote:
I use DEBUG 0 and 1 for the same reasons as you and have never had the fault
you mention.
If you could send me, privately, a copy of your program I'll try to locate
the problem.
Thanks for your offer of help, this is
In message 1329572303.66299.yahoomail...@web171520.mail.ir2.yahoo.com,
Michael Bulford michaelbulf...@yahoo.co.uk writes
Hi George
On Saturday 18 February 2012, 9:56George Gwilt wrote:
I use DEBUG 0 and 1 for the same reasons as you and have never had
the fault you mention.
If you could
There is some code in my program that I do not want compiled: this is only used
when the SuperBASIC version is running. So, I use DEBUG 1 before the code and
DEBUG 0 afterwards. When compiling the parser stops with the report of
Task Turbo 5.06 halted, after line 0. Reason: out of range
In message 1329506713.90809.yahoomail...@web171507.mail.ir2.yahoo.com,
Michael Bulford michaelbulf...@yahoo.co.uk writes
There is some code in my program that I do not want compiled: this is
only used when the SuperBASIC version is running. So, I use DEBUG 1
before the code and DEBUG 0
12 matches
Mail list logo
