Re: [CFCDev] Init Methods on CFCs

[Brian Kotek]

Actually when creating a Java class, the init() method is *not* called automatically. Creating a reference to a Java class and not calling init() allows you to invoke static methods on that class. You must call init() to actually run the constructor. That's part of the reason why CFCs have standardized on using init(): so that calling the constructor for CFCs and Java classes is handled using the same syntax.

On 5/8/06, Nando <[EMAIL PROTECTED]> wrote:

In Java, the init() function is called automatically when an instance is of an object is created. In CF, it is not - it's just a convention. It's up to the developer to remember to call it. The purpose of the convention is to give us a common method to use to initialize an object, so we understand our own and each other's code more easily. The purpose of chaining the init() call by convention is to group object instantiation with it's initialization, like Java does automatically.

----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to cfcdev@cfczone.org with the words 'unsubscribe cfcdev' as the subject of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).

An archive of the CFCDev list is available at www.mail-archive.com/cfcdev@cfczone.org