armedbear-devel

armedbear-devel@common-lisp.net

1 participants
1200 discussions

[armedbear-devel] abcl-1.1.0 vs. abcl-1.1.0.2 known differences
by Mark Evenson 26 Jan '13

26 Jan '13

To address a question that came up on #abcl: what is the difference between the abcl-1.1.0 and abcl-1.1.0.2 releases? The short answer is that there should be no difference. The release of abcl-1.1.0 (and accompanying signatures) were updated "in-place" within twenty-four hours of their release. As stated in the abcl-1.1.0.2 release announcement, the only known initial difference between the 1.1.0 and 1.1.0.2 releases of ABCL was that somehow the ABCL-CONTRIB ASDF definition in 1.1.0 was syntactically invalid as it included an extra comma (",") character preventing it from loading. After this was discovered, the abcl-1.1.0 release was rebuilt and "updated" in place on common-lisp.net. Because googlecode requires that published URIs point idempotently to their resources over time (probably to make universal distribution easier) a release designated abcl-1.1.0.2 release was made to googlecode.com If there are any observed differences between the two releases, I would appreciate knowing more details accompanied by information on how the distribution was obtained. -- "A screaming comes across the sky. It has happened before, but there is nothing to compare it to now."

1 0

[armedbear-devel] Upgrade issues
by Faré 25 Jan '13

25 Jan '13

ABCL is one of the three implementations, together with CLISP and CMUCL, where I ultimately punted on ASDF hot-upgrade, by just trying to rename away the ASDF package if it's too old. I don't know if you're interested in making the kind of package surgery I was indulging in work, but it involves rehoming symbols from ASDF to subpackages such as ASDF/COMPONENT, including for class slot names. Anyway, please test the latest ASDF with ABCL, I think it's ripe for release, but I'd like your feedback considering the massive amount of hacking that happened. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org If the human mind were simple enough to understand, we'd be too simple to understand it. — Pat Bahn

4 7

[armedbear-devel] Android support?
by Andrew Pennebaker 22 Jan '13

22 Jan '13

What's the state of Android support for ABCL? Can we have some demo apps and tutorials? It would be awesome to write mobile apps in Lisp! -- Cheers, Andrew Pennebaker www.yellosoft.us

1 0

Re: [armedbear-devel] [asdf-devel] CMUCL fails tests (Was Re: Just pulled an update and now CCL fails the tests)
by Faré 20 Jan '13

20 Jan '13

> I guess its yet another issue with merging with *d-p-d* which defaults > to #p"" (current directory) on cmucl. > > Ray > Yup. Fixed. Which reminds me I have no implementation of getcwd for ABCL or GCL; I don't know what type it returns on Corman. ABCL hackers: is there such a thing as getcwd in ABCL, and if so how do I get to it? —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org A pretty face is not a passport; it's a visa and it runs out fast.

2 1

[armedbear-devel] Pre ASDF-2.27 failing to compile on ABCL
by Mark Evenson 15 Jan '13

15 Jan '13

On 1/11/13 5:53 PM, Faré wrote: > Dear Lisp hackers, > > I've completed yet another major pass of refactoring of ASDF. […] Coolness! Keep it coming! Failing to compiled the concatenated fasl from ASDF master tip (local : UNDEFINED-FUNCTION: ;COMMON-LISP:CELL-ERROR-NAME triggers autoloading of org.armedbear.lisp.cell_error_name ... ; Autoloaded org.armedbear.lisp.cell_error_name (0.0050 seconds) The function ASDF/PACKAGE::WHEN-FISHY is undefined. Have I missed some packaging in the implemenation (abcl-1.2.0-dev)? ABCL trunk currently has some problems with autoloading (some) COMMON-LISP functions via SETF expanders, which I am in the process of fixing. ; SLIME 2012-11-23 CL-USER> (lisp-implementation-version) "1.2.0-dev" "Java_HotSpot(TM)_64-Bit_Server_VM-Sun_Microsystems_Inc.-1.6.0_37-b06" "amd64-SunOS-5.11" Thanks, Mark <evenson(a)panix.com>

1 0

[armedbear-devel] function (setf documentation) has disappeared
by Eric Marsden 06 Jan '13

06 Jan '13

Hi, It seems that the DEFSETF for DOCUMENTATION has disappeared recently. -- Eric Marsden

2 3

[armedbear-devel] default-initargs not respected for funcallable-standard-class
by Pascal Costanza 05 Jan '13

05 Jan '13

Hi, What the subject line says. Here is a test case: CL-USER(1): (use-package :mop) T CL-USER(2): (defclass my-method (standard-method) ()) #<STANDARD-CLASS MY-METHOD {1EE9DE5F}> CL-USER(3): (defclass my-generic-function (standard-generic-function) () (:metaclass funcallable-standard-class) (:default-initargs :method-class (find-class 'my-method))) #<FUNCALLABLE-STANDARD-CLASS MY-GENERIC-FUNCTION {6E06D676}> CL-USER(4): (defgeneric my-function () (:generic-function-class my-generic-function)) #<MY-GENERIC-FUNCTION MY-FUNCTION {2EA1569}> CL-USER(5): (generic-function-method-class #'my-function) #<STANDARD-CLASS STANDARD-METHOD {4E513D61}> The reason is that the defaulting happens in the keyword arguments for ensure-generic-function (in clos.lisp), which thus overrides any default initargs. However, the defaulting should be left to the class. Pascal -- Pascal Costanza

2 6

[armedbear-devel] PortableAserve on ABCL
by Dave Cooper 05 Jan '13

05 Jan '13

Happy New Year everybody! Welp it seems my porting binge which started over the holidays isn't quite settling down yet... So. What are the chances of getting Portableaserve to work in ABCL? Note that I'm not asking if there are better ways of serving web from ABCL (I'm sure there are). I'm just asking specifically about portableaserve on ABCL. Any opinions if this is within the realm of possibility, or would there be some obvious show-stopper? I guess most of the challenge would be getting an acl-compat working for ABCL... -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

2 1

[armedbear-devel] soap calls using java interop
by Kevin Raison 04 Jan '13

04 Jan '13

I am having trouble getting certain aspects of a soap client working using abcl's java interop; most likely, this is the result of my ignorance of how certain things map from java to lisp. Any help would be appreciated! The soap service is defined by this wsdl: http://chatsubo.net/~raison/usaepay.wsdl. The provider has a java library available for download at http://wiki.usaepay.com/developer/soap-1.4/howto/javajaxws. I have been able to use this library successfully in abcl (creating objects, calling methods on those objects, etc.), except when I need to call any of the methods defined in the java.rmi.Remote UeSoapServerPortType interface. For example, the method addCustomer is defined in the files http://chatsubo.net/~raison/UeSoapServerBindingStub.java and http://chatsubo.net/~raison/UeSoapServerPortType.java. No matter how I try to find the method (using jcall or various combinations of jmethod and class refs), I simply cannot find this method. What am I missing here? Thanks for any assistance! -Kevin -- Kevin Raison Founder Chatsubo.net, LLC http://chatsubo.net/ (p) 206-801-5728 (f) 206-801-5729

2 2

[armedbear-devel] ABCL on Android?
by Nitralime 04 Jan '13

04 Jan '13

Is there any effort to port ABCL to Android? Regards Nik

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel