On Wed, Mar 21, 2012 at 11:09 AM, Alexandre Bergel
alexandre.ber...@me.comwrote:
This is interesting. If we have this method on Object, can it be used to
keep track of side effects? It looks like to isn't it?
For doing that, you should access any object in a byte-indexed way, I
don't know
I discovered that String implements #crc16, which adapted for my needs (as
#crc16from:to:), it's faster than my Adler implementation, so I moved.
cheers,
Martín
On Wed, Mar 28, 2012 at 4:15 PM, Martin Dias tinchod...@gmail.com wrote:
On Wed, Mar 21, 2012 at 11:09 AM, Alexandre Bergel
This is interesting. If we have this method on Object, can it be used to keep
track of side effects? It looks like to isn't it?
Alexandre
Le 19 mars 2012 à 23:35, Martin Dias tinchod...@gmail.com a écrit :
Finally I tried with a bytecodes checksum to detect changes. I chose a 16-bit
Finally I tried with a bytecodes checksum to detect changes. I chose a
16-bit variant of Adler-32 (http://en.wikipedia.org/wiki/Adler-32). Was
easy and worked fine.
ByteArray
adler16from: start to: end
Answer a checksum over the values of the specified interval, calculated
using Adler-16
Hi
In Fuel (bleeding edge), a compiled method can be serialized as a global.
Basically, we store the class name and selector, so loading it is
straightforward... this can be fine if we suppose there were not any change
in the system between save and load time. This can be a huge supposition,
but
