On Tue, 6 Dec 2011, Henrik Sperre Johansen wrote:
On 06.12.2011 16:35, Mariano Martinez Peck wrote:
On Tue, Dec 6, 2011 at 4:30 PM, Henrik Sperre Johansen
<[email protected] <mailto:[email protected]>> wrote:
On 06.12.2011 15:55, Mariano Martinez Peck wrote:
On Mon, Dec 5, 2011 at 4:21 PM, Stefan Marr <[email protected]
<mailto:[email protected]>> wrote:
Hi:
I got here a Monticello package that does not properly load
using the Metacello configuration. The image freezes and
cmd+. does not pop up a debugger anymore.
Is there a way to force Monticello/Metacello to fall back on
the included source instead of using the binary snapshot? (I
guess that is going wrong for some reason).
Not very elegant, but you can delete the .bin from the .mcz file,
and it should fall back to importing from sources.
The binary snapshot is only for the definitions. The source is
always get from the .sources.
I'm not sure what you mean, but the source compiled when you
install an MCDefinition, is taken from the .bin if that was the
source of it. (its source instvar is a string, not a pointer to
source location in .sources file).
It seems I was wrong. All I wanted to say is that the final representation
of code (classes, compiled methods, etc) are compiled from source code.
The snapshot does not include a "binary represenation of the code". The
code is always needed. What I thought is that it was always from sources.st
<http://sources.st> , but you say it can be from the bin as well.
Yup!
OT: Which, as you surely know, is also why a more radical
rethinking/restructuring than the neat experiment Tobias Pape posted recently
is needed if one wanted to take full advantage of a Fuel monticello format :)
Eliminate the compilation step, and mcz loading would probably be FAST!
5% faster? :)
Levente
Cheers,
Henry
