[Openmcl-devel] My beach balls runneth over

[John McAleely]

I've held off from responding on this thread for a while, but your  
description of using the IDE and finding it very unstable is exactly  
the experience I had a couple of months ago.

I would have been using 1.2, so when you reported 1.3 was similar, I  
was assuming the work in trunk might make my experience irrelevant.  
However, now that it seems that some users of trunk can use it  
successfully, while you see instability means I do at least want to  
observe that I saw the same sort of problems you see.

My usage was a Saturday spent prototyping non critical (and very  
newbie) code. I resolved not to touch the IDE again until the current  
work package was concluded. (My production use of CCL is all via the  
command line).

I assumed all IDE users experienced the same problems, and that my  
lack of experience would reduce the value of bug reports, given that  
more experienced people would also find these. If that is not the  
case, I am inclined to find some time to play a little more in my  
setup and see if I can create reproducible bugs, rather than simply a  
long winded 'me too' posting on this list.

J


On 19 May 2009, at 22:53, Ron Garret wrote:

>
> On May 19, 2009, at 2:40 PM, Ron Garret wrote:
>
>>
>> On May 19, 2009, at 2:16 PM, Raffael Cavallaro wrote:
>>
>>
>>> I don't see any of this. I'm running trunk though. Maybe you  
>>> should switch?
>>>
>>
>> Trying that now.  For the record, the version I was running came  
>> from the instructions on http://trac.clozure.com/openmcl:
>>
>> The preferred way to get Clozure CL is via Subversion. For example,  
>> to get Clozure CL 1.3 for Darwin/x86, you'd type (where the $ is  
>> the shell prompt):
>>
>> $ svn co http://svn.clozure.com/publicsvn/openmcl/release/1.3/darwinx86/ccl
>>
>> If people should be running the trunk this probably ought to be  
>> changed or I'm not going to be the only one having these problems.
>>
>> Also for the record, I can tolerate a certain amount of instability  
>> at the moment if problems like this are being fixed relatively  
>> quickly (like hours to days rather than weeks to months).  I'm not  
>> doing anything mission-critical right now, so it's actually a good  
>> time for me to be a guinea pig.
>>
>
> Youch!  Brain wedgie.  Of course, the trunk *is* the bleeding edge.
>
> rg
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20090519/244e6adc/attachment.htm>