It makes sense, there is no reason for RB to store a copy of the code for each object method, only the properties and me value change with each instance. This must be very similar to what RB is now doing for shared methods! Except of course you couldn't get any shared properties with that method alone.
Math On 3/15/06, Charles Yeomans <[EMAIL PROTECTED]> wrote: > > When you call an object method using a nil object reference, REALbasic > raises a NilObjectException. If, however, nilObjectChecking is set to > false in a pragma statement, what should happen? What does happen is > that the method is called and executes, and RS says that this is the > correct behavior. Upon reflection it appears that this isn't so > unreasonable; I suppose at some level this is equivalent to calling the > method with (secret) first parameter nil. So is the real danger here > that a method called on a nil reference might attempt to access object > properties? These are I believe available via pointer navigation from > the object address, but when the address is 0... _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
