Am 27.01.2013 um 18:34 schrieb Wolfgang Lenerz: > Mainly, SMSQmulator is slow because: > > 1 - I'm trying to to things with Java for which is wasn't really designed > (painting single pixels to a "screen", low level byte,word access to > variables and memory, etc).
In Java you also have to shift double the amount of data around, because Java doesn't know about "unsigned" data types (a serious omission, IMHO) Don't know if this helps you in some way: The logic e.g. uqlx uses is to collect all the changed scan lines (i.e. areas of memory) during a screen operation and update only changed scan lines in one go after the end of the op. (That's done as a bitmap operation, then) > 3 - I'm by far not the programmer Marcel is. Considering your day job and judging by the results, you're very, very good for a non-professional ;) >> As the java machine has a built-in garbage collector timings are going >> to be erratic as the whole java machine suddenly stop while it does the >> garbage collection. > > Perhaps, but I doubt it. I've yet to see such a phenomenon. Those times have long gone by - This used to be a problem in very early Java implementations. The quirk has long gone, but the myth still remains ;) Regards, Tobias _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
