[Openmcl-devel] My beach balls runneth over
ralex at cs.colorado.edu
Wed May 20 01:41:47 UTC 2009
I have spent quite a bit of time with the CCL 1.3 IDE. While there are
some occasional glitches overall the IDE is pretty usable. Closing the
AltConsole window has been a problem in most cases. Basically, I never
close it. A clear output button would be nice.
On May 19, 2009, at 8:46 PM, Ron Garret wrote:
> I think "very unstable" is putting it much too harshly. I've
> encountered what appears at the moment to be two problems, one of
> which I think is well on the way to being solved, and neither of
> which seems to be affecting anybody but me. My impression is that
> the IDE is very nearly ready for prime time, at least for my needs.
> I'm pretty close to going back to CCL as my primary development
> On May 19, 2009, at 3:07 PM, John McAleely wrote:
>> 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.
>> 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.
>>> Openmcl-devel mailing list
>>> Openmcl-devel at clozure.com
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
Prof. Alexander Repenning
University of Colorado
Computer Science Department
Boulder, CO 80309-430
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openmcl-devel