28 Oct
2014
28 Oct
'14
8:31 p.m.
On 28.10.2014, at 20:28, Levente Uzonyi leves@elte.hu wrote:
On Tue, 28 Oct 2014, Tobias Pape wrote:
On 28.10.2014, at 17:23, commits@source.squeak.org wrote:
Item was changed: ==== ERROR ===
Error: Unrecognized class type
Well, this is gonna be interesting in the future. Are SPUR MCZs now completely incompatible to non-spur MCZs?
This would be terrible…
No, but Spur has new class formats which are not recognized by SqueakSource. I shouldn't be hard to fix it for someone who knows how SqueakSource works, and what the new formats are.
SqueakSource uses the available Monticello. This obviously means that the “old” monticello is incompatible to the Class formats of SPUR, right?