Re: [Ql-Users] Quanta Magazine
Hi George and others who have also missed the Apr/May issue of QUANTA eMag, After considerable investigation, it would appear that having sent the Apr/May Issue of QUANTA eMag out in two batches, I may have sent the same batch out twice! Some time ago, I sent out the eMag out as one batch but together with a large .PDF file I was advised by BT that I had exceeded some limit that I wasn't aware of and it was suggested that I sent the eMag out in two batches. Of course the error with the recent issue is entirely my fault for which I apologise to all affected and both John Southern and I have tried to keep pace with the messages received telling us that they had not received their eMag. I think that most of you know that I have resigned from the QUANTA Committee as treasurer and Membership Secretary with effect from the A.G.M. in April and John Southern has taken over from me. Good luck John! However, just in case anyone has still not received their eMag, I have decided to send the eMag again to all the members who were on the second mailing list. To those who have already received the eMag, I offer my sincere apologies for any inconvenience caused by receiving a duplicate attachment. Hopefully having corrected the error, I only have to say thank you to all who have helped me with my QLing and should any of you have a problem with anything that you think I can answer (or know someone who can), please drop me an email and I will endeavor to provide either a full answer or perhaps a key from which you can sort out your problem on your own. To you all, I hope that you continue to get a load of pleasure from your QL and I look forward to following your activities either through this list or through the QUANTA Magazine . Cheers and kind regards, John Gilpin. On 24/07/2017 16:56, George Gwilt wrote: On 24 Jul 2017, at 16:52, John Gilpin> wrote: My fault entirely. - See attached Thank you George ___ QL-Users Mailing List
[Ql-Users] Subject: Re: PCB Design v7.52
Whenever I try to run any new SBASIC code, there is this overlapping problem of some variable names used are possibly already installed as resident procedures. The code then either does not work as intended, or can stop with an error message. In these circumstances, I usually have to go through the code and rename the variables. Compiling into machine code can solve the above mentioned problem. I first of all compiled using Turbo. There was one REFERENCE statement that had to be inserted for the procedure Rotation, which passes back the values x and y to the caller, FreeRotate, which by the way is not even called. There was just one expression at line 1230 that had to be re-written, to avoid Turbo using integer arithmetic and stopping with an overflow error. The resulting task seems to work as well as the SBASIC version. Next I tried Q-Liberator, which compiled the code easily enough. The resulting object file fails to display the x and y coordinates at the bottom of the screen. Both Turbo and Q-Liberator issued a Warning at line 23030 of .. END IF without an IF. A few weeks back I made mention about a new proposed update to the Turbo parser, which I have almost finished tweaking. I tried this new version on the code, and this did not warn of the above condition. It did however, give information messages about how variables are being used - being the difference between Interpreted code and Turbo code. It transpires that if one wants the SBASIC code to match exactly what the Turbo version does, then a great deal of changes will need to be made. I only have one criticism of the program so far. When the program ends it does a NEW. I may have made some changes or added some REMarks, and before closing down I would SAVE the code. But after a NEW, all the code has gone! The existing file is replaced with a blank one. Michael ___ QL-Users Mailing List