[Openmcl-devel] Clozure CL 1.2 released - type of cocoa-application ?
james anderson
james.anderson at setf.de
Sun Sep 21 14:12:46 PDT 2008
On 2008-09-21, at 15:17 , Gail Zacharias wrote:
> There is some discussion of this in http://trac.clozure.com/openmcl/
> ticket/208 and http://trac.clozure.com/openmcl/ticket/87. It looks
> like the problem is not implementation as much as thinking it
> through and deciding what's right.
i don't know, but - reading those comments, maybe one is expecting
too much from it.
just reading the code, the notes, that output would go to the
console, seem right-minded.
if one puts a handled call to startup-ccl (or its equivalent) just
before starting the event loop, that seems as late as possible before
anything visible has happened. if something goes wrong, output
appears on the console (somehow it's sometimes the ccl and sometimes
the system console) and in any case the first listener appears. this
is certainly enough to be useful.
>
>
> At 9/21/2008 12:06 PM, james anderson wrote:
>> hello;
>>
>> when one starts the ide, it does not follow the documented
>> initialization protocol. that is, the init file is not loaded.
>>
>> if one incorporates the simple init file loading logic from start-ccl
>> into the toplevel-function for a cocoa application, that succeeds.
>> is some reason to avoid this?
>> is there some reason that one would not want to add the call to
>> start-
>> ccl at that point?
>>
>> the code describes a situation, wherein the only argument is a
>> process identifier, but one could extract startup parameters out of
>> the info.plist file. it's straight-forward to do, just a bit fragile
>> should an error occur.
>>
>> any reason - other than the problems with error handling at that
>> stage, to not do this?
>>
>> thanks,
>>
>> _______________________________________________
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
>> http://clozure.com/mailman/listinfo/openmcl-devel
>
More information about the Openmcl-devel
mailing list