Re: [Fwd: RFC GDL2: move +load implementations to +initialize]

[Mirko Viviani]

David Ayers <d.ayers@inode.at> ha scritto:

> I don't have an app complex enough to test regressions (and the 
> guile-gdl2 regression testing tool I'm working out now was ironically 
> the executable bitten) but I believe it to be sane to assume that before 
> an EODatabaseChannelNeededNotfication is posted, that EODatabseChannel 
> should have recieved an +initialize and before an 
> EOCooperatingObjectStoreNeeded is posted, than EODatabaseContext should 
> have been initialized.

Why the EODatabaseChannel should have received the +initialize before the
notification of the EOObjectStoreCoordinator ?
You should invoke it manually, it has no sense.

> If not, then we might in insure all expected 
> initializes have been sent in some startup function that we somehow 
> guarantee to be called early in GDL2 initialization.

I don't know of a different function than +load to do the job.
Remember that I can only use EOControl without EOAccess (ok, maybe not now),
why do I have to force the developer to call +initialize method of these
classes ?

> Here's a patch to move the +load implementations to +initialize.

Not applied.

-- 
Ciao
Mirko