Subject: Re: Using filenames which contain wildcard characters - msg#00101

Previous Message by Date: click to view message preview

eBay Auction Education -- genus budorcas

ir ajriywspv wxvf s g djfog rkydrtmmzzfigchsurxzdqqdx

Next Message by Date: click to view message preview

Re: Clisp 2.29 segmentation fault on OSX after 120 recursions

> * In message <FA147D13-66FD-11D7-9B09-000393B6680C@xxxxxxxxxxxxx> > * On the subject of "[clisp-list] Clisp 2.29 segmentation fault on OSX after > 120 recursions" > * Sent on Sat, 5 Apr 2003 02:31:43 +0200 > * Honorable Frank Sonnemans <clisp@xxxxxxxxxxxxx> writes: > > I have a somewhat puzzling problem with CLISP 2.29 (installed using > FINK) on Mac OSX. > > My first test function (fact) gives a segmentation fault after about 120 > recursions. (fact 100) works, but (fact 120) gives a seg. fault. > > I tried setting the memory limit higher to 200MB, but the problem > remained. Even on the default 2 MB stack I am surprised that it would > crash so quickly. Does anyone know the cause / solution of/to this > problem. try rebuilding it with libsigsegv. see <http://clisp.cons.org/faq.html#stack> -- Sam Steingold (http://www.podval.org/~sds) running RedHat8 GNU/Linux <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html> Never underestimate the power of stupid people in large groups. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf

Previous Message by Thread: click to view message preview

Using filenames which contain wildcard characters

Hi everyone, I've hit a bit of a stumbling block with some code I'm working on. I have a file called "hello?.txt" (unix filesystem) that I'm trying to open using (with-open-file ..), but I'm getting the following: [1]> (with-open-file (test "hello?" :direction :input)) *** - wildcards are not allowed here: #P"hello?" Is there some way to escape the '?' character that I'm missing? I've been through the impnotes, and mined the archives of this list and c.l.l but haven't had much luck turning up answers. Relevant details: GNU CLISP 2.30 (released 2002-09-15) (built 3248584626) (memory 3258512962) running Debian unstable. Features: (ASDF MK-DEFSYSTEM COMMON-LISP-CONTROLLER CLX-ANSI-COMMON-LISP CLX CLOS LOOP COMPILER CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI UNICODE BASE-CHAR=CHARACTER SYSCALLS PC386 UNIX) Thanks for reading, any help is greatly appreciated. Mark -- Mark Triggs <mst@xxxxxxxxxxxxxxx> ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

Next Message by Thread: click to view message preview

Re: Using filenames which contain wildcard characters

Pascal Bourguignon <pjb@xxxxxxxxxxxxxxxxx> writes: > Sam Steingold writes: [...] >> CLHS is quite explicit on OPEN: >> >> An error of type file-error is signaled if (wild-pathname-p filespec) >> returns true. >> >> It is possible to add an keyword option to OPEN to circumvent it, but >> it will not be portable. >> Maybe it would be better to avoid such pathnames? Absolutely, but unfortunately I'm at the mercy of whatever bogus names people have decided to give their files :o) > Or to use a unix API (linux package in clisp). See the current POSIX > thread on comp.lang.lisp... Thanks for the suggestions. Given that the hyperspec makes it clear that an error should be signalled (sorry to have missed that), the behaviour is understandable. The linux package should do the trick for my purposes anyway. Thanks again, Mark -- Mark Triggs <mst@xxxxxxxxxxxxxxx> ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf