From: Sam S. <sd...@gn...> - 2004-10-06 17:38:58
|
> * Bruno Haible <oe...@py...t> [2004-10-06 19:07:11 +0200]: > > Sam wrote: >> > But the C function physical_namestring should check against >> > wildcards. It makes no sense to pass namestrings like >> > "/foo/**/*.lisp" to the system, because wildcard handling, needs to be >> > done in clisp, not by the system's open() function. >> >> what if the user wants to pass "/foo/*.lisp" to shell? > > He can do so. That's not what the function physical_namestring() is > used for. Grep for all uses of physical_namestring(), you'll see what > I mean. I know how it is used. I introduced this function myself. ;-) Now, suppose a win32 loser creates a file named "what do I do next?.csv" Can CLISP open this file? -- Sam Steingold (http://www.podval.org/~sds) running w2k <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.honestreporting.com> UNIX, car: hard to learn/easy to use; Windows, bike: hard to learn/hard to use. |