Oddities in Cocoa/Java object initialization?
Oddities in Cocoa/Java object initialization?
- Subject: Oddities in Cocoa/Java object initialization?
- From: email@hidden
- Date: Tue, 26 Jun 2001 23:01:35 -0400
I have a Java sub-class (twice removed) of NSDocument that seems to have
two unexpected initialization behaviors (at least I didn't expect them):
1) Two constructors -- the no-arg constructor and the two arg (filename
and type) seem to be getting called when the document is constructed;
2) A private data member (a boolean flag that's supposed to be
initialized to "false") is getting "initialized" to false *after* the
constructor(s) is(are) executed. This seems backward from the normal
behavior of Java classes.
Are these behaviors perhaps a consequence of inheriting from Objective-C
classes?
Thanks in advance...
Doug Knowles