Re: [Ql-Users] QD 2018

Thank you, Marcel - ! On Sun, 16 Sep 2018 at 00:55, Marcel Kilgus via Ql-Users < ql-users@lists.q-v-d.com> wrote: > I have just updated QD 2018 to version B.05: > > ; B.05 Implemented per-extension editor-usage (configurable) (MK) > ; Fixed BASIC usage for DEFine FuNction (MK) > ;

Re: [Ql-Users] sBASIC overloading...

Im not familiar with C++ overloading, but S*BASIC allows some "parametric polymorphism", viz: dim x%(2): for i% = 0 to 2: x%(i%) = 9 - i% Test 'abc', 2.99, x% : def proc Test(a, b%, c) print a\ b% \ c, \ enddef Test : Result: abc 2.99 9 8 7 The SBASIC compiler performs a number of additional

Re: [Ql-Users] Fwd: Re: Theme file format

As mentioned, the suggested binary standard would be in addition to the established text standard as used by QCoCo. Its easy enough to convert files back and forth between these formats. So pundits and punters are free to choose. A possible advantage with having a header, such as "THB9" (where 9 =

Re: [Ql-Users] Theme file format

Sorry, that was supposed to be: header dc.b "THB",57; not "THM",57 data dc.w $200 dc.w $FFC0 etc.. On 13 November 2017 at 17:59, Per Witte wrote: > > Theme file format > > I had a look at Theme file format on QL forum. Some > > comments and

Re: [Ql-Users] Theme file format

> Theme file format > I had a look at Theme file format on QL forum. Some > comments and questions: > > Rethorical question: Is it worthwhile to create a new > format to save some space (a few bytes, I suppose) > when we have (QPC2, SMSQmulator) 128MB at our disposal? Despite computers getting

Re: [Ql-Users] Strange channel bugs?

Is this the sort of issue you mean? 100 CLS 110 FOR i = 0 TO 4 120 FOR j = 0 TO 4 130 AT i * 2, j * 6: PRINT i; ','; j; 140 END FOR 150 END FOR 160 : 170 PRINT 180 PAUSE RUNs fine under SMSQ/E, displays only the first line if compiled as a Qlib job (but no errors or warnings are given -

Re: [Ql-Users] EXT_PROC

Thanks Dilwyn. It seems Jon S is already on the case of appending it. Per On 9 November 2017 at 20:19, Dilwyn Jones via Ql-Users < ql-users@lists.q-v-d.com> wrote: > I've OCRed Chapter 15 from my copy of the manual and placed it as PDF and > Word DOC file at

Re: [Ql-Users] EXT_PROC

Chapter 15!? On 9 November 2017 at 00:03, Bob Spelten via Ql-Users < ql-users@lists.q-v-d.com> wrote: > Op Wed, 08 Nov 2017 21:05:55 +0100 schreef Per Witte via Ql-Users < > ql-users@lists.q-v-d.com>: > > I was just made aware of a number of features in Q-Lberat

Re: [Ql-Users] EXT_PROC

t; > 2017-11-08 21:05 GMT+01:00 Per Witte via Ql-Users < > ql-users@lists.q-v-d.com> > : > > > I was just made aware of a number of features in Q-Lberator that I havent > > seen documented anywhere: EXT_PROC, EXT_FN, GLOBAL, and possibly others. > I > > believe

[Ql-Users] EXT_PROC

I was just made aware of a number of features in Q-Lberator that I havent seen documented anywhere: EXT_PROC, EXT_FN, GLOBAL, and possibly others. I believe I have a general idea of what theyre about, but should like to see some documentation. Ive been told there is a chapter 14 in some manuals?

Re: [Ql-Users] SMSQmulator 2.25

Great! Im particularly pleased that many of the differences in behaviour between SMSQmulator and QPC2 have been ironed out! That means that programmers dont have to write separate versions, or include fiddly workarounds, in their programs. They run identically on both platforms. Amazingly, this

Re: [Ql-Users] Stupid AND

Yes, its dumb, but the problem has been there since the day day dot. So suck it up and work around :) Per On 19 September 2017 at 21:55, Wolfgang Lenerz via Ql-Users < ql-users@lists.q-v-d.com> wrote: > On 19/09/2017 21:32, Dave Park via Ql-Users wrote: > >> Your BASIC interpreter fits in 48K.

Re: [Ql-Users] Qbase

Lots of different programs use Qmenu, so there should be no need to link it in. Its best loaded at boot time. Per On 19 September 2017 at 21:15, Wolfgang Lenerz via Ql-Users < ql-users@lists.q-v-d.com> wrote: > Hi, > > the problem is that these parameters are likely to vary from version to >

Re: [Ql-Users] EasyPTR vs Button Frame :-)

PS You will probably also need some kind of toolkit to reserve and release a slot in the Button Frame. If you dont have one and dont feel like writing your own, you may use mine. Its just over 300b of code. Per On 4 September 2017 at 23:02, Per Witte wrote: > Yes, but not

Re: [Ql-Users] EasyPTR vs Button Frame :-)

Yes, but not with Wman. You have to devise your own. Per On 4 September 2017 at 20:20, Giorgio Garabello via Ql-Users < ql-users@lists.q-v-d.com> wrote: > Hello to all. > Has anyone ever tried to insert an EasyPTR menu inside the Button Frame? > Is it possible? > > Greetings > Giorgio >

Re: [Ql-Users] TURBO and testing it exists

Hi Michael, I dont know why it doesnt work for you. I just clicked on the link now and it works for me. Try copying the link and pasting it in your browser. The article is about searching for specific keywords in SuperBASIC, SBASIC and compiled BASIC without the use of an external toolkit. Per PS

Re: [Ql-Users] TURBO and testing it exists

was not just a thoughtless blurt. Per On 19 August 2017 at 09:13, George Gwilt via Ql-Users < ql-users@lists.q-v-d.com> wrote: > > > On 18 Aug 2017, at 17:38, Per Witte via Ql-Users < > ql-users@lists.q-v-d.com> wrote: > > > > George, the question is relevant if y

Re: [Ql-Users] TURBO and testing it exists

George, the question is relevant if you write programs intended for other people: You cant be sure THEY will load Turbo. However, IMHO, any serious Tinkerer should load Turbo as a matter of course. Per On 18 August 2017 at 16:54, gdgqler--- via Ql-Users < ql-users@lists.q-v-d.com> wrote: > > >

Re: [Ql-Users] TURBO and testing it exists

Thats a nice solution. Not sufficient for all manner of keywords, though. A more general solution for checking for relevant toolkits in boot programs, without having to load a toolkit to do so can be found in this article: http://www.hunggartorino.it/ql/findkey/ (also available in Italian!) Per

Re: [Ql-Users] Function type error

I couldnt resist wading in here. Regarding Michael's original question the Mint% routine should answer.Try this: 100 : 110 a = 330.7: b = 440.7 120 PRINT #0, Min_Int%(a, b), Mint%(a, b) 130 PAUSE -1 140 STOP 150 : 160 DEFine FuNction Min_Int%(x%,i) 170 IF x% < i : RETurn x% : ELSE : RETurn i 180