Re: [Ql-Users] Finding the line number in QPC2

2013-11-28 Thread Michael Bulford
Hi since there seems to be no way to get at this with Peek and Poke, I've made a small SBasic extension to tget the value on the return stack, called RET_STK and RET_STK2: You can download this extension from www.wlenerz.com/QLStuff I’ve tried this. From inside a function it

Re: [Ql-Users] Finding the line number in QPC2

2013-11-27 Thread Wolfgang Lenerz
Hi, I'd love to be proved wrong, but I don't think it can be done. (You can't even get the current line nbr from Sbasic, unless I'm mistaken). Mucking about with the return stack will lead to nothing much, I'm afraid. Wolfgang Sometimes my programs will stop with a nice friendly error

Re: [Ql-Users] Finding the line number in QPC2

2013-11-27 Thread Wolfgang Lenerz
Hi, The QL's SuperBasic interpreter and SMSQ/E's Sbasic are VERY different beasts, even if the latter tries to keep program compatibility! Wolfgang I'm surprised that no one has responded to this yet. Both QDOS and SMSQ/E (which is what QPC2 does), have the same look and feel to the

Re: [Ql-Users] Finding the line number in QPC2

2013-11-27 Thread Wolfgang Lenerz
Hi, since there seems to be no way to get at this with Peek and Poke, I've made a small SBasic extension to tget the value on the return stack, called RET_STK and RET_STK2: A small extension to get the line number of the line having called a function or procedure, in an Sbasic program. USE:

Re: [Ql-Users] Finding the line number in QPC2

2013-11-26 Thread Timothy Swenson
I'm surprised that no one has responded to this yet. Both QDOS and SMSQ/E (which is what QPC2 does), have the same look and feel to the operating system and almost all SuperBASIC code will work on both OS's. The Turbo compiler and toolkit work on both OS with no issues (that I am aware of).

[Ql-Users] Finding the line number in QPC2

2013-11-26 Thread Michael Bulford
Hi all I’m sorry about my previous message – I had forgotten to use plain text, and this appeared garbled. Hopefully, with any luck, this should now be transmitted correctly. Here is how the message should have been ...   Sometimes my programs will stop with a nice friendly error message,