[Glass] LargeObjectNode instances

James Foster smalltalk at jgfoster.net
Wed Dec 15 08:11:33 PST 2021


No, it is not expected that an instance of LargeObjectNode no longer responds to messages such as #asOop. Here is what I get in 3.6.2:

(Metaclass3 allInstances detect: [:each | each name asString = 'LargeObjectNode class']) thisClass allInstances any asOop “3546113”

James

> On Dec 15, 2021, at 2:37 AM, Johan Brichau via Glass <glass at lists.gemtalksystems.com> wrote:
> 
> Hi,
> 
> Another question in the context of upgrading a repository from GemStone 2.4.4.1 to 3.4.5:
> 
> Is it expected that instances of the hidden class LargeObjectNode no longer respond to messages such as #asOop?
> 
> In GemStone 2.4.4.1, when we get a reference to an instance of the hidden class LargeObjectNode responds to messages such as #asOop.
> After converting the repository to GemStone 3.4.5, sending #asOop to instances of the hidden class LargeObjectNode result in a DNU.
> 
> We hit it because we have a script to verify the conversion by listing instances of ‘orphaned’ classes. 
> Since LargeObjectNode is a hidden class, it shows up in that script, but I wanted to verify if it is normal that this class LargeObjectNode is empty? It also has an empty method dictionary is a new install in GemStone 3.4.5, so I expect it to be normal but wanted to make sure ;-)
> 
> Best regards
> Johan
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> https://lists.gemtalksystems.com/mailman/listinfo/glass



More information about the Glass mailing list