[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problem with subseq
- To: UNM42E@IBM.rhrz.uni-bonn.de
- Subject: Problem with subseq
- From: michael@rhein.iam.uni-bonn.de (Michael Stoll)
- Date: Fri, 23 Jul 93 16:01:04 +0200
- Resent-date: Fri, 23 Jul 93 15:53:09 MEZ
- Resent-from: Michael Stoll <UNM42E@IBM.rhrz.uni-bonn.de>
- Resent-message-id: <9307231358.AA04750@ma2s2.mathematik.uni-karlsruhe.de>
- Resent-to: clisp-list@ma2s2.mathematik.uni-karlsruhe.de
----------------------------Original message----------------------------
Bela Pecsek <P2043742@csdvax.csd.unsw.EDU.AU> writes:
[Stuff deleted]
> *** - SUBSEQ: :END should be an integer >=0, not NIL
>
> After this error I grebbed the subseq function from the CMU Common Lisp
sources
> and compiled and loaded it. I tested it first of course and it seems to work
> just fine.
[Tests deleted]
> But then I wanted to start up Gilt and guess what happened?
> The Gilt Work Window, Gilt Commands and Gilt Motif Gadgets came up and I was
> happier than ever and then the shock came.
>
> > (gilt:do-go)
>
> *** - SUBSEQ: :END should be an integer >=0, not NIL
> 1. Break>
>
> I realy don't know where this error comes from but hopefully somebody out
there
> knows about it.
[Stuff deleted]
Propbably the calls to `subseq' have been compiled inline, so that the built-in
subseq function is called even if you have redifed subseq later.
Try to declare subseq notinline (for example, (proclaim '(notinline subseq)) )
and recompile.
Michael