So I have the following two systems running in abcl (ported from the ACL versions).

the Direct Memory Access Parser http://www.cs.northwestern.edu/academics/courses/325/readings/dmap.php

and

The Reactive Action Packages see for example, this paper
http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=7&ved=0CFkQFjAG&url=http%3A%2F%2Fciteseerx.ist.psu.edu%2Fviewdoc%2Fdownload%3Fdoi%3D10.1.1.53.9428%26rep%3Drep1%26type%3Dpdf&ei=weB_U_qhBLSnsQTpm4DQAg&usg=AFQjCNHsc7zv5z2m99BGAt97AIiD7jrrgw&sig2=zdPEAC-wJPNmXy2F7Z_d1Q&bvm=bv.67720277,d.cWc&cad=rja

I get them all to load and run, but there are some glitches with compiling the files that I'm still working out.

I want to thank everyone on this list who helped me in recent days.
Pete
Hi Pete,

No problem. Let me know if you need help. If you don't and succeed, let us know if you've been successful and what you're using ABCL for. Always interested.

Regards,

Erik.


On Thu, May 22, 2014 at 8:32 PM, bonasso <bonasso@traclabs.com> wrote:

Erik,
It was an example from the app.
I'm working it out.  This app has a big make file that has lots of cruft in it from past years.  I'm cleaning it up and (with help from you guys) making progress.
If I get stuck I'll let you know.
Pete
Hi Pete,


On Thu, May 22, 2014 at 8:28 PM, bonasso <bonasso@traclabs.com> wrote:

Erik,
Thanks.  I'm trying to get an ACL system I've used for years to run under abcl.  ACL allows defpackage to augment previous package properties...

As I said, it's probably not optimal. What behaviour were you depending upon that ACL allows which ABCL doesn't? Exactly the behaviour in your example? Or was that just for demonstration?

Regards,


Erik.
 
Pete
Hi Peter,

On Thu, May 22, 2014 at 7:05 PM, bonasso <bonasso@traclabs.com> wrote:

In Common Lisp, I believe defpackage is to either define or *redefine* a package.

Actually, ...
 
  I've found that in abcl if the package is already defined, defpackage won't redefine it (apparently).

... That's correct CLHS compliant (though not mainstream behaviour) -- as per the CLHS:

      If the new definition [of the existing package being named]  is at variance with the current state of that package, the consequences are undefined
 

Is this a bug?


Undesirable maybe, given the deviation from what's accepted mainstream, but strictly not a bug.


--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.




--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.




--
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.