Re: RMCL 5.2 on Snow Leopard: floating point issues

>At 15:25 +0300 18.10.2009, Toomas Altosaar wrote:
>>Are you saying you are getting floating point problems after calling
>>(choose-directory-dialog) with 10.5 or are you just saying you also
>>get spinning beach ball kind of behaviors with 10.5?
>
>I have not noticed any floating point inconsistencies in 10.5 with MCL 5.1b.
>
>I just thought it very interesting that fp problems sprung up in 
>10.6 only after calling _NavDialogRun in RMCL ... and that 
>_NavDialogRun is also giving problems in MCL 5.1b4 (beach-ball since 
>MCL waits for a semaphore that never is activated).
>
>So it seems that the callback was somewhat screwy in 10.5, and that 
>10.6 is even more stringent/critical of misuse.
>
>I have not checked with Console to see if any "this call deprecated" 
>messages are being logged.


I just got hung again when calling (choose-file-dialog) in MCL 5.1b4 
running 10.5.8.

Yes, the Console does have three messages pertaining to MCL's hang:

20.10.09 4:36:21 PM Focus.image[1462] *** -[NSConditionLock 
unlockWithCondition:]: lock (<NSConditionLock: 0x5a2adb90> '(null)') 
unlocked from thread which did not lock it
20.10.09 4:36:21 PM Focus.image[1462] *** Break on _NSLockError() to debug.
20.10.09 4:36:21 PM Focus.image[1462] *** Break on _NSLockError() to debug.

So some things need to be rethought in RMCL (if its a problem there).

The event timer is running, so this might be the problem.

Side note: Recent Carbon List entries show that some people have 
problems with the event timer not firing anymore on 10.6.
_______________________________________________
info-mcl mailing list
[email protected]
http://clozure.com/mailman/listinfo/info-mcl