Evening Dilwyn, > I remember poor Albin Hessler trying to demonstrate Easyptr to me at a > meeting in Germany at some point (Munster?). It's always difficult as a developer/programmer (whatever the correct term is these days!) to demonstrate something to the general public. The developer knows everything about the program and the public don't have a clue, and seemingly, never will. The developer gets frustrated at this as it's "all so simple". Never the twain shall meet!
> I was still not much the > wiser. Actually, it wasn't so much "Easyptr" which was difficult, rather > the baseline QPTR programming principles and terminology and the like. There's a pretty good introduction to the PE on your web site! :-) > Easyptr at all, or at least it would have taken longer. Your tutorial > put the EASY into Easyptr. Well, strangely, I still use it myself at times! > Yes, it couldn't handle missing last parameters - where the list of > parameters ends with a separator, so you had to add a dummy parameter. That was it, yes! > IIRC it was a QLiberator issue, not an Easyptr one, so programs ran OK > under the interpreter and cuased much gnashing of teeth (to put it > politely) when they didn't work compiled. My problem exactly. I had your Calculator program running quite happily under the interpretor, but compiling it and running that simply blew up in your face! Most frustrating. > Of course, these days, you can choose to write using QPTR, TurboPTR or > EasyPtr. And there's a few packages designed to make some of these > easier to use,like the PE Kit, SPACE and the like. PE Kit - that's got my Easy Pointer tutorial on it - must be good! > As you might guess from the fairly consistent appearance of my programs, > I have a set of modules I bolt together to form the core of most of my > programs. Saves having to reinvent the wheel each time. Always wise to re-use debugged modules. Cheers, Norman. _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
