Dear George
Another of interest
John
----- Original Message -----
From: "P Witte" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, April 09, 2005 3:27 PM
Subject: Re: [ql-users] Q-Starter
> Marcel Kilgus writes:
>
> > [EMAIL PROTECTED] wrote:
> > > The latest beta test version of Turbo, v4d21, should soon be on the
> SQLUG
> > > site. This one has compiled QPTR's "demo_bas" (after some
> modifications).
> >
> > I'm curious, what kind of modifications? Dimensioning of strings?
> > I've read the readme of v4c21 and it sounds pretty promising. What
> > grade of compatibility do you think you'll be able to achieve?
>
> It sounds very promising! It must also be a major achievement as, IIUC,
> Turbo gains some of its speed advantage by not mimicking certain
SuperBasic
> interpreter structures. Are these structures now being emulated by Turbo?
> And without a significant speed penalty?
>
> > EasyPtr has sometimes a very powerful but also very complex syntax,
> > e.g.
> >
> > {} = alternative
> > [] = optional
> >
> > MAWDRAW [#ch%] {,}{;}{\} num[, [array$][, xst%, yst%[, [under%]
> > [, [xsz%], [ysz%][, [xju%][, [yju%]]]]]]]
> >
> > MAWDRAW #3,1,array$,0,0,,,16
> >
> > but I think it only passes back simple integers or integer arrays in
> > its parameters (with MINPUT being the only exception, it alters a
> > given string using SB.PUTP). Could Turbo manage all this stuff?
>
> All EasyPtr keywords can return an error code in the channel parameter,
> provided it is supplied as an integer, ie #ch%. However, it gets more
> complicated: You can set EasyPtr up so that instead of a channel number
you
> pass a pointer to the working definition. A designated variable then gets
> any error code instead!
>
> 100 adr = MWDEF(#ch%)
> 110 REPeat loop
> 120 ch% = 0
> 130 action = MCALL(#adr)
> 140 if ch% < 0: PRINT 'Error during MCALL:'! ch%: EXIT loop
> ...
>
> Luckily, both these behaviours are optional. Their main use is for aiding
> program development. Turbo should now be able to handle the first scenario
> in any case. But it probably doesnt handle the second?
>
> The main stumbling block was that Turbo couldnt handle arrays being passed
> as parameters. With this considerable inconvenience overcome, a major
> disincentive to use Turbo has been removed.
>
> Per
>
> _______________________________________________
> QL-Users Mailing List
> http://www.q-v-d.demon.co.uk/smsqe.htm
_______________________________________________
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
