compiler error

Hello, All!

while compiling UCW with ABCL 0.0.7 got following error:

The value "<tr
  ><th
    >Index</th
  ><th
    >Description</th
  ><th
    >Locals</th
  ><th
    >Source</th
  ></tr
>" is not of type SIMPLE-STRING.
   [Condition of type TYPE-ERROR]

backtrace:

 25: (INVOKE-DEBUGGER #<TYPE-ERROR {17EE7D5}>)
 26: (JVM::WRITE-CONSTANT-POOL #<FILE-STREAM {1838550}>)
 27: (JVM::WRITE-CLASS-FILE #S(JVM::CLASS-FILE :PATHNAME
"H:\\lisp\\ucw\\ucw_dev\\src\\rerl\\request-loop-error-21.cls" :LAMBDA-NAME
NIL :CLASS "org/armedbear/lisp/request_loop_error_21" :SUPERCLASS
"org/armedbear/lisp/Primitive" :LAMBDA-LIST (MOP::ARGS MOP::NEXT-EMFUN)
:POOL NIL :POOL-COUNT 1 :POOL-ENTRIES #<EQUAL hash table, 306 entries, 767
buckets {FC652E}> :FIELDS NIL :METHODS (#S(JVM::JAVA-METHOD :ACCESS-FLAGS
NIL :NAME "execute" :DESCRIPTOR
"(Lorg/armedbear/lisp/LispObject;Lorg/armedbear/lisp/LispObject;)Lorg/armedb
ear/lisp/LispObject;" :NAME-INDEX 1 :DESCRIPTOR-INDEX 2 :MAX-STACK 11

Re: compiler error

On Wed, 3 Aug 2005 at 00:29:09 +0300, Alex Mizrahi wrote:
> Hello, All!
>
> while compiling UCW with ABCL 0.0.7 got following error:
>
> The value "<tr
>   ><th
>     >Index</th
>   ><th
>     >Description</th
>   ><th
>     >Locals</th
>   ><th
>     >Source</th
>   ></tr
> >" is not of type SIMPLE-STRING.
>    [Condition of type TYPE-ERROR]
>
> backtrace:
>
>  25: (INVOKE-DEBUGGER #<TYPE-ERROR {17EE7D5}>)
>  26: (JVM::WRITE-CONSTANT-POOL #<FILE-STREAM {1838550}>)
>  27: (JVM::WRITE-CLASS-FILE #S(JVM::CLASS-FILE :PATHNAME
> "H:\\lisp\\ucw\\ucw_dev\\src\\rerl\\request-loop-error-21.cls" :LAMBDA-NAME
> NIL :CLASS "org/armedbear/lisp/request_loop_error_21" :SUPERCLASS
> "org/armedbear/lisp/Primitive" :LAMBDA-LIST (MOP::ARGS MOP::NEXT-EMFUN)
> :POOL NIL :POOL-COUNT 1 :POOL-ENTRIES #<EQUAL hash table, 306 entries, 767
> buckets {FC652E}> :FIELDS NIL :METHODS (#S(JVM::JAVA-METHOD :ACCESS-FLAGS
> NIL :NAME "execute" :DESCRIPTOR
> "(Lorg/armedbear/lisp/LispObject;Lorg/armedbear/lisp/LispObject;)Lorg/armedb

abcl build support for openmcl

here's a patch that adds openmcl as a build host
for abcl-0.0.7.

     ..bryan

--- build-abcl.lisp.0	2005-08-14 11:24:41.000000000 -0700
+++ build-abcl.lisp	2005-08-14 11:39:11.000000000 -0700
 <at>  <at>  -121,7 +121,25  <at>  <at> 
 (defun run-shell-command (command &key directory (output *standard-output*))
   (excl:run-shell-command command :directory directory :input nil :output output))

-#+(or sbcl cmu lispworks)
+#+openmcl
+(defun run-shell-command (command &key directory (output *standard-output*))
+  (when directory
+    (setf command (concatenate 'string
+                               "\\cd \""
+                               (namestring (pathname directory))
+                               "\" && "
+                               command)))
+  (multiple-value-bind (status exitcode)
+      (ccl:external-process-status
+       (ccl:run-program
+        "/bin/sh"
+        (list  "-c" command)
+        :wait t
+        :input nil :output output))
+    (declare (ignore status))

Re: abcl build support for openmcl

On Sun, 14 Aug 2005 at 11:46:48 -0700, bryan o'connor wrote:
> here's a patch that adds openmcl as a build host
> for abcl-0.0.7.

Committed.

Thanks!

-Peter

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Any new version of j?

Hi,

I am a big fan of J, since 2003. It's my preferred editor, period.

I see this forum quite is quite alive, but the last binary version of j is about
a year old. Is there any new version, even in developing stages?

Thanks a lot for such a wonderful tool.

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Any new version of j?

On Wed, 24 Aug 2005 at 20:17:12 +0000, mg wrote:
> Hi,
>
> I am a big fan of J, since 2003. It's my preferred editor, period.
>
> I see this forum quite is quite alive, but the last binary version of
> j is about a year old. Is there any new version, even in developing
> stages?

There's a development snapshot (j 0.21.0.4) from June 1:

    http://armedbear.org/j.zip          (source)
    http://armedbear.org/j-jar.zip      (just j.jar)

I'm hoping to release abcl 0.0.8 in the next week or so, and I'll
probably put up another development snapshot of j shortly thereafter.

-Peter

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Re: Any new version of j?

Peter Graves <peter <at> armedbear.org> writes:

> 
> There's a development snapshot (j 0.21.0.4) from June 1:
> 
>     http://armedbear.org/j.zip          (source)
>     http://armedbear.org/j-jar.zip      (just j.jar)
> 
> I'm hoping to release abcl 0.0.8 in the next week or so, and I'll
> probably put up another development snapshot of j shortly thereafter.
> 
> -Peter
> 

I'll try it soon. Thank you!

-Marcelo

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

Bug 1276665

Bug 1276665:

> Initial Comment:
> I'm really liking Armed Bear Lisp except for the fact
> that it lacks logical pathnames.  Any idea when this
> functionality is going to be implemented?

In a word, no.

It must be done eventually, of course, but I've been putting it off,
out of lack of interest (both on my part and, until now, on the part of
ABCL's users).

I can't predict with any certainty when I might get around to it, but
it might be a good project for a short vacation, and I've got one of
those coming up real soon now, as soon as 0.0.8 is released.

> I'm a decent Java programmer and would not mind
> implementing this myself.  In fact I am much more so a
> Java programmer than a  Lisper.  If I understood
> logical pathnames better, I'd give it a shot.
> Could you thumbnail what I'd need to do in order to
> implement it?

It's all spelled out (FSVO "all spelled out") in the specification:

    http://www.lispworks.com/documentation/HyperSpec/Body/19_.htm

ABCL's general policy in most things is to strive to emulate SBCL's
behavior on platforms that SBCL supports; unfortunately logical

ABCL 0.0.8

ABCL 0.0.8 is now available:

    http://armedbear.org/abcl.html

The main user-visible change in this release is that by default, the
.cls files generated by the compiler are now zipped up into their
parent .abcl file.

For example:

    $ unzip -v tailp.abcl
    Archive:  tailp.abcl
     Length   Method    Size  Ratio   Date   Time   CRC-32    Name
    --------  ------  ------- -----   ----   ----   ------    ----
         254  Defl:N      202  21%  08-30-05 11:15  f59bc191  tailp._
        1174  Defl:N      559  52%  08-30-05 11:15  b59ff9af  tailp-1.cls
    --------          -------  ---                            -------
        1428              761  47%                            2 files

You might want to think of tailp.abcl, in the new system, as tailp.jar;
the file tailp._, within the archive, would have been tailp.abcl in the
old system.

When you use build-abcl.lisp to build abcl.jar, the per-.abcl
compression is not done, in order to end up with only a single level of
compression in abcl.jar; if you look in src/org/armedbear/lisp, you'll
see the .cls files and unzipped .abcl files that were zipped up into
abcl.jar.

When you compile the Lisp source files of your application, on the

Good luck on the project, ABCL