So this mean this is more of a warning than an error and it does not really affect the installation of NBOpenGL ?
and what it means by "invalid state for a small period" ? is that a bytecode issue or an object issue ? Camillo Bruni-3 wrote > yeah we have to have solve this somehow, it is a side-effect of the new > class-builder > which actually properly validates the layouts of classes. > > If you modify classes with monticello they might end up in an invalid > state for a short > period. Previously this went undetected, the SlotClassBuilder is very > picky about this :(. > > Maybe an intermediate solution for this is to disable any kind of > validation while we > load stuff with Monticello... > > On 2013-09-11, at 15:13, kilon < > [email protected] > > wrote: > >> IcompatibleLayoutConflict: Class with PointerLayout cannot be extended as >> byte >> >> is the error i am getting using the very latest pharo 3.0 image while >> trying >> to load NBOpengl >> >> (ConfigurationOfNBOpenGL project version: '2.0') load. >> >> here is the full trace >> >> http://pastebin.com/an4KFVrH >> >> I get the same error in macos and ubuntu, I suspect windoom is same too. >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/NBOpengl-Error-IcompatibleLayoutConflict-tp4707721.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > > > > signature.asc (457 bytes) > <http://forum.world.st/attachment/4707735/0/signature.asc> -- View this message in context: http://forum.world.st/NBOpengl-Error-IcompatibleLayoutConflict-tp4707721p4707745.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
