I'm getting reports from some Mac Intel users that my project only
runs around 33% faster than perl.
On the G5, it is definitely 4-5x faster, though.
Sorry for the outrageous claims ;) Well I did state that it was G5
only claims, but still I could have waited.
And also, ElfData is not going away. I will make it more relevant
over time. I've already got lots of ideas for making dealing with
streams, a very common thing, much easier.
I've previously absolutely avoided adding file, socket and stream
code to ElfData, as a clear design decision to make ElfData very easy
to compile on all platforms, being just data-only. Now I've seen that
this has actually hurt the usage of ElfData, because it adds to the
number of lines needed to interface with write and read to files. But
I believe, that if I use RB functions, and cache the results, process
them intelligently, then I can get some big speed ups, AND result in
code that is actually uses just as few lines of code for streaming as
RB does currently.
I'd be very interested to see how RB's BinaryStream compares to C's
fread function. If there's any gains to be made via fread, you can be
sure ElfData will capitalise on it ;)
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
