Re: Bugzilla 586, the fast char replacement (was Revolution compilation)
On Jan 8, 2005, at 11:33 AM, Dar Scott wrote: On Jan 8, 2005, at 11:59 AM, Michael D Mays wrote: Ag..., I was doing put into char to 4448 of x put into char to 4447 of x LOL! I suspected that, so I carefully counted on my fingers. -- Dar Dar, you have 4447 fingers? (running away) regards, Geoff Canyon [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Bugzilla 586, the fast char replacement (was Revolution compilation)
Are you saying that replacing 4 chars is fast or should be fast? I can't make it fast. If it is suppose to be fast how do you do it? Michael On Jan 4, 2005, at 12:02 PM, Dar Scott wrote: On Jan 4, 2005, at 10:00 AM, Michael D Mays wrote: 0.04 -- yy 10MB at char 999 Yes. Perhaps a small growth near the end can be optimized some day. (Appending small amounts is fast on the average.) I think that replacing 4 chars for 4 chars is fast. Think imageData pixel. I think that replacing 8 chars with 8 chars is fast. Think matrix. Dar ** DSC (Dar Scott Consulting Dar's Lab) http://www.swcp.com/dsc/ Programming Services and Software ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Bugzilla 586, the fast char replacement (was Revolution compilation)
On Jan 8, 2005, at 8:30 AM, Michael D Mays wrote: Are you saying that replacing 4 chars is fast or should be fast? I can't make it fast. If it is suppose to be fast how do you do it? on mouseUp put longString(10) into x put the long seconds into a -- OS X timing only put into char to 4447 of x put the long seconds into b put b-a end mouseUp function longString n put empty into s repeat n times put x after s end repeat return s end longString == .08 (Mmmm. This and single char are faster than last week, but the time grows slightly the first few times.) You have to replace a char chunk with the same size string. The timing test needs to be modified for Windows. A crude timer: Make a loop around the 'put' and do it 10,000 times and then divide the delta seconds by 10,000. Dar ** DSC (Dar Scott Consulting Dar's Lab) http://www.swcp.com/dsc/ Programming Services and Software ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Bugzilla 586, the fast char replacement (was Revolution compilation)
Ag..., I was doing put into char to 4448 of x Michael On Jan 8, 2005, at 12:24 PM, Dar Scott wrote: put into char to 4447 of x ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Bugzilla 586, the fast char replacement (was Revolution compilation)
On Jan 8, 2005, at 11:59 AM, Michael D Mays wrote: Ag..., I was doing put into char to 4448 of x put into char to 4447 of x LOL! I suspected that, so I carefully counted on my fingers. -- Dar ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Bugzilla 586, the fast char replacement (was Revolution compilation)
This is good for a single char but beware if you say something like put yy into char 12345 you see a tremendous slow up: 0.08 -- y 100KB at char 9 0.13 -- y 10MB at char 999 0.000412 -- yy 100KB at char 9 0.04 -- yy 10MB at char 999 But this is good to know. I had some running sums which really dragged on moderate sized data sets. But when I say put char i of tt into char 99444+i of x things really speed up. On my tests one char inset took 13 microseconds and 15 chars using a repeat loop took 37 (on a 10MB string) Michael On Jan 3, 2005, at 8:52 PM, Dar Scott wrote: Concerning bugzilla 586, the fast char replacement... On Jan 3, 2005, at 7:00 PM, Alex Tweedly wrote: So 2 questions 1. Is this fix already in 2.5 ? Yes. Here is a timing demo for OSes that have a high res long seconds: on mouseUp put longString(10) into x put the long seconds into a -- OS X only put y into char of x put the long seconds into b put b-a end mouseUp function longString n put empty into s repeat n times put x after s end repeat return s end longString == .14 The fix is really an enhancement. Either I goofed and labeled it a bug or it got turned into a bug by another. 2. Where in BZ do you look for that info ? I think that is normally the target milestone. Some of those fell in a crack, but currently, those those are getting set. ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Bugzilla 586, the fast char replacement (was Revolution compilation)
On Jan 4, 2005, at 10:00 AM, Michael D Mays wrote: 0.04 -- yy 10MB at char 999 Yes. Perhaps a small growth near the end can be optimized some day. (Appending small amounts is fast on the average.) I think that replacing 4 chars for 4 chars is fast. Think imageData pixel. I think that replacing 8 chars with 8 chars is fast. Think matrix. Dar ** DSC (Dar Scott Consulting Dar's Lab) http://www.swcp.com/dsc/ Programming Services and Software ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Bugzilla 586, the fast char replacement (was Revolution compilation)
Concerning bugzilla 586, the fast char replacement... On Jan 3, 2005, at 7:00 PM, Alex Tweedly wrote: So 2 questions 1. Is this fix already in 2.5 ? Yes. Here is a timing demo for OSes that have a high res long seconds: on mouseUp put longString(10) into x put the long seconds into a -- OS X only put y into char of x put the long seconds into b put b-a end mouseUp function longString n put empty into s repeat n times put x after s end repeat return s end longString == .14 The fix is really an enhancement. Either I goofed and labeled it a bug or it got turned into a bug by another. 2. Where in BZ do you look for that info ? I think that is normally the target milestone. Some of those fell in a crack, but currently, those those are getting set. ** DSC (Dar Scott Consulting Dar's Lab) http://www.swcp.com/dsc/ Programming Services and Software ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
