Re: [Ecls-list] Slime build failure (Was: Project status)
On Sun, Dec 12, 2010 at 5:23 AM, Matthew Mondor wrote: > On Sat, 11 Dec 2010 14:55:21 -0500 > Matthew Mondor wrote: > > > I'll also try with an up to date slime when I have more time, but I > > wanted to post this in case the origin of the problem seems obvious to > > others. > > It also happens with today's SLIME CVS HEAD and an empty ~/.eclrc I identified the problem and fixed it. Slime is building pathnames with components of type (array character (*)) while the operating system (or at least the ECL routines) only accept (array base-char (*)). I have added a filter that coerces all strings in pathnames to the second type if possible. If it is not possible, then those filenames are using characters beyond the 256 lowest Unicode codepoints, which is not accepted by ECL. Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Slime build failure (Was: Project status)
On Sun, 12 Dec 2010 20:09:13 +0100 Juan Jose Garcia-Ripoll wrote: > I identified the problem and fixed it. Slime is building pathnames with > components of type (array character (*)) while the operating system (or at > least the ECL routines) only accept (array base-char (*)). I have added a > filter that coerces all strings in pathnames to the second type if possible. > If it is not possible, then those filenames are using characters beyond the > 256 lowest Unicode codepoints, which is not accepted by ECL. I could indeed see the ECL_BASE_STRING_P() check in enter_directory() but had no idea how come that case wasn't problematic before or with other software. After your fix, I could test current ECL with current SLIME and confirm they work great together again :) Thanks again, -- Matt -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
Re: [Ecls-list] Slime build failure (Was: Project status)
On Sun, Dec 12, 2010 at 9:40 PM, Matthew Mondor wrote: > I could indeed see the ECL_BASE_STRING_P() check in enter_directory() > but had no idea how come that case wasn't problematic before or with > other software. > Maybe there was some normalization phase in older versions of ECL (somewhere converted from string to base-string), or Slime was using base strings, or you built it without Unicode (the problem was only present when ECL distinguished between base-char and character) Juanjo -- Instituto de Física Fundamental, CSIC c/ Serrano, 113b, Madrid 28006 (Spain) http://juanjose.garciaripoll.googlepages.com -- Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL, new data types, scalar functions, improved concurrency, built-in packages, OCI, SQL*Plus, data movement tools, best practices and more. http://p.sf.net/sfu/oracle-sfdev2dev ___ Ecls-list mailing list Ecls-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ecls-list
