So it seems my expectation wasn't unreasonable (I expected Pharo to do the same
as Smalltalk/X - given you can leave an undeclared reference). Perhaps Marcus
might be able to comment on this, and I'll go and see if its been written up as
an existing bug and if its also present in Pharo 12 now th
I created a method referring to a non-existent "Snark" class.
To my astonishment, "Code Search|References to it" quietly failed to
do anything visible.
It didn't find it, and it didn't say that it couldn't find it.
However, "Code Search|Method source with it" DID find the reference.
Pharo 9 and Pha
*If* you can locate one example, you may be able to manually examine the
compiled method itself to see what distinguishes it in terms of the
reference to a missing object. e.g. what's in the literal pool for a method
which references a non-existent class? You could create one such example
explicitl
Tim,
Another anomaly I found with the above, even with my code that does not
reference the missing classes - but is contained within the same package of
classes that do reference the missing classes (clear?)... my application
crashes with an error that the reference could not be found. This may be
