I wanted to run a test: a CallSubDelayed on an object-variable referring to an object that "no longer exists" (?).
So I created a B4J project "on the fly" and I came across some rather strange things (one of which I don't even write... at least for now).
It is not easy to explain in words what the problems are, so I am attaching the project, which is very simple (B4J).
A class has an object variable which refers to an object instantiated elsewhere.
This object is set to null. If inside the class I use a CallSubDelayed "to the variable", the method is executed as if the object still exists.
I used to love Canada.
The weather is not like the stereotype. Toronto is more to the south than Rome! It's nice and hot in the summer. The fall is also great. The problem is that winter is long, spring is just a few days and it happens at the end of May.