26 Jan
2012
26 Jan
'12
3:29 p.m.
On Thu, Jan 26, 2012 at 12:28 PM, Nick Ager <nick.ager(a)gmail.com> wrote:
Hi Davorin,
One idea I came up with is to build an exporter which generates Pier kernel
creation code based on the data currently in Pier - it's a lazy design as I
only have to write an exporter not an importer. I've used it successfully on
a few smaller projects but have yet to try it on more substantial projects.
...
I will add PRKernelCodeExporter
class>>#exportMigratedKernel: which will
generate #prototypeInstance initialisation for PRComponents, but first I'd
like feedback if people think this approach is worth pursuing in theory and
if so, in practice does the PRKernelCodeExporter work on your existing
kernels?
I can not look at it more deeply now, but it seems to me like a good
idea, because if something goes wrong with import (if being close to
rhetorical;), one would probably be able to hack the generated code by
hand until it can create valid PRKernel instance. Which might be
simpler than hacking the binary representation in file, or
transforming the somehow mis-loaded object tree in memory.
I have one ancient Pier 1.x kernel on which I might try that, once I
find some time. Do you think that PRKernelCodeExporter might have a
chance working on old kernels (there has been some variables
additions, removing, etc).
Davorin
http://www.cloud208.com/