Mikko Ahonen wrote:
Hello,
Small issue I seem to constantly run into while debugging Cells source code:
First, I sometimes get "New as of Cells3: parent must be supplied to
make-instance of .." for various reasons.
Hmmm. That is just the family class, yes? If you are not specifying the
:fm-
Hello,
Small issue I seem to constantly run into while debugging Cells source code:
First, I sometimes get "New as of Cells3: parent must be supplied to
make-instance of .." for various reasons. For example now I used c? for
cell that did not refer to any other cell. Anyway, this is expected.
B
[ccing cells-devel because usefully on topic]
Peter Hildebrandt wrote:
Me, too. The question is why can't you just abort the backtrace, fix the
mistake, and re-run. You mentioned you had to restart Lisp, obviously a bad
thing, but not my case so I am wondering ...well, I'll keep reading.
So w
On 5/15/08, Ken Tilton <[EMAIL PROTECTED]> wrote:
> Ken Tilton wrote:
>
>
> > For me it is just abort/fix/rerun.
> >
Me too -- unless cells gets into this Current DP is not GE pulse
business -- then I can't figure out how to fix that.
Peter
> I meant "with Celtk".
>
> kt
>
>
__
Ken,
thanks for the quick response.
> I have not put any thought into recovery. We could certainly do something
> primitive like simply not make such a big fuss over the error, either
> allowing the setf with a big noisy warning about "don't think you just
> triggered some dataflow", or /not/ al
Peter Hildebrandt wrote:
Every now and then I do something silly (like setf'ing a cell w/o
initializing it as c-in, and I run into a cells-stop.
What is the correct way to recover from this?
I have not put any thought into recovery. We could certainly do
something primitive like simply not ma
Every now and then I do something silly (like setf'ing a cell w/o
initializing it as c-in, and I run into a cells-stop.
What is the correct way to recover from this?
I used to do a (cells-reset), but all too often the next cells
operation runs into something like that:
Current DP 28 not GE pulse