armedbear-devel

armedbear-devel@common-lisp.net

1199 discussions

[armedbear-devel] Re: What are you working on?
by Rolando Pereira 08 Apr '15

08 Apr '15

ubikation _ <ubikation-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org> writes: > What projects are people working on using ABCL? If they are > open-source, would you mind sharing a link to the repository? Since the lack of answers is slightly disappointing I guess I can post something regarding an experiment I did an afternoon a couple months ago which tried to link Jython to ABCL. Since it was an experiment I didn't put the source code online. Also currently the source is basically just a "*slime-scratch*" buffer saved to a file which means that the code is a hairy mess. But here's an example to show how to use it: > (add-to-classpath "/home/rolando/src/jython/jython-standalone-2.5.3.jar") > (defvar *interpreter* (jss:new 'org.python.util.PythonInterpreter)) > > (#"exec" *interpreter* "import feedparser") > > (defvar *rss-parse* (gethash "parse" > (py-unwrap (#"getDict" > (gethash "feedparser" > (py-unwrap (#"getLocals" *interpreter*))))))) > > ;; Get the ABCL mailing list RSS > (defvar *rss* (pycall *rss-parse* "http://rss.gmane.org/gmane.lisp.armedbear.devel")) Having defined the "*rss*" variable you can then do this: > CL-USER> (gethash "title" (nth 1 (gethash "entries" (py-unwrap *rss*)))) > "Web frameworks with ABCL (was Re: SBCL->ABCL migration questions)" > T Something I wanted to make was importing the Python modules as Lisp functions so instead of defining the "*rss-parse*" as > (defvar *rss-parse* (gethash "parse" > (py-unwrap (#"getDict" > (gethash "feedparser" > (py-unwrap (#"getLocals" *interpreter*))))))) you could do: > (feedparser:parse "http://rss.gmane.org/gmane.lisp.armedbear.devel") and that would also allow you slime's autocomplete to complete the python code. I've thought about doing the above using a macro around the "inspect" Python module, but never got around to it. Best Regards, Rolando Pereira

1 0

[armedbear-devel] MQTT example using ABCL and Eclipse Paho
by Frederico Munoz 08 Apr '15

08 Apr '15

Hi all, I have written a simple example of using the Eclipse Paho libraries, via ABCL, to send messages in Common Lisp using MQTT. I will not write much more here since it's in the article which contains the code and some other considerations: http://finisterra.motd.org/?p=237 As I note I initially did this in Clojure so - and just like my experiments with Swing before which I sent to the list as well - this is in a way a comparison on how the interop facilities work. My code is not exactly stellar (either the Clojure or the CL one) but it is, I hope, easy enough to understand and follow, especially since I couldn't found any other example out there, which is why I thought the list could have some use for it (even if only for future reference). I stumbled a bit on getting the command-line arguments but that was due to my custom-made abcl script end with $@ instead of "@" - something to watch for :) I had one problem that I found weird and which I would welcome any help, I'm not sure why the following works: CL-USER(3): (#"currentThread" 'Thread) #<java.lang.Thread Thread[interpreter,5,main] {BD30B16}> ... but the following doesn't: CL-USER(4): (#"sleep" 'Thread 100) #<THREAD "interpreter" {19AA4D78}>: Debugger invoked on condition of type ERROR no such method Restarts: 0: TOP-LEVEL Return to top level. For another short demo I have I will need to subclass, something used in Swing programming a lot from what I could understand. If I'm not mistaken this isn't currently supported in ABCL, but I will read on it. Best regards, Frederico

3 3

[armedbear-devel] Java 6+ Type-checking bytecode verifier compatible output: requirements analysis
by Erik Huelsmann 08 Apr '15

08 Apr '15

Hi all, At ECLM the other week, Alessio and I agreed to start working on a requirements analysis regarding the output required for the type-checking bytecode verifier. We know Mark wants to create an intermediate level code representation to address any issues that may arise. However, we want to assess requirements first and come up with a solution after that. That solution may or may not depend on such an intermediate representation. For now, we'd like to leave that undecided. So, what I learned that the type-checking bytecode verifier wants is that it can verify the state of the stack and of the locals for all bytecode instructions. In order to do so, it needs: 1. The "initial state" of stack and locals at the external entry points of a function (ie notably the start and any exception handlers) 2. Optional "state modifications" when locals start being used or when the flow from one instruction to another is broken (such as in case of (conditional) jumps) Apart from a different class file version number and an attribute to store this information in, that's it. More doesn't the verifier want to know. Is it your understanding as well that this is all that is required? -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0

[armedbear-devel] c++ library FreeLing from ABCL
by Alexandre Rademaker 08 Apr '15

08 Apr '15

I am trying to use a C++ library called FreeLing from ABCL (using the library JAVA API). I have just posted a question in http://stackoverflow.com/questions/17556912/calling-freeling-java-api-from- abcl. Does anyone know of any limitation of ABCL to deal with the System.load of Java? Best, Alexandre

3 7

[armedbear-devel] Bug: COND clauses must have a test
by Pascal J. Bourguignon 08 Apr '15

08 Apr '15

The syntax for COND is: cond {clause}* => result* clause::= (test-form form*) therefore (cond ()) should be a program-error, but abcl 1.0.1 returns NIL. -- __Pascal Bourguignon__ http://www.informatimago.com/

2 1

[armedbear-devel] Next steps on our way to usability
by Erik Huelsmann 08 Apr '15

08 Apr '15

Hi all, With support for CloserMOP now almost released (great job! Thanks Rudi, Pascal and everybody who helped out!), I'm looking forward to see how we can run more quicklisp packages. If you look at http://common-lisp.net/project/cl-test-grid/abcl/abcl-1-2-0-load-failures.h… and the load failures recently published for 1.2.0, you'll see that the root blockers now (apart from cl-glfw-opengl-core<http://cl-test-grid.appspot.com/blob?key=1fgcximsyj> which fails due to a missing dynamic library) portability libraries: uffi, iolib.base, kmrcl, acl-compat and metatilities. Seems we're looking for people who want to submit portability code to these projects! Bye, Erik.

2 2

[armedbear-devel] Some convenience functions
by Theam Yong Chew 08 Apr '15

08 Apr '15

Hi all, I've got a bunch of useful functions for general hacking with abcl. Hope they could be useful. Any suggestions on the best place for sending patches (if indeed they are useful enough). abcl contribs, slime contribs, or core abcl? Yong ;; javap seems to be bundled/more widely available compared to the defaults (defun disassemble-class-cmd (path) (with-accessors ((d pathname-directory) (n pathname-name)) (merge-pathnames path) (format nil "cd ~{/~a~}; javap -c ~a" (cdr d) n))) (defun disassemble-class (path) (ext:run-shell-command (disassemble-class-cmd path))) (setf system::*disassembler* #'disassemble-class-cmd) (in-package :swank) (defmethod menu-choices-for-presentation ((throwable java:java-exception)) "Java exception stack traces (different from Lisp stack traces) are also available." (list (list "printStackTrace" (lambda (choice object id) (declare (ignore choice id)) ;; TODO, print to an Emacs buffer instead (java:jcall "printStackTrace" *standard-output* (java:java-exception-cause object)))))) (in-package :swank-backend) ;; Not real frame local variables, but it at least exposes function ;; arguments for possible inspection (defimplementation frame-locals (index) (loop for id upfrom 0 for item in (java:jcall "toLispList" (nth-frame index)) collect (let () ;; ((id id) (item item)) (list :name "??" :id id :value item)))) (defimplementation frame-var-value (index id) (elt (java:jcall "toLispList" (nth-frame index)) id))

2 1

[armedbear-devel] ABCL 1.2.1 Release
by Mark Evenson 08 Apr '15

08 Apr '15

We think that [abcl-1.2.1][] represents the final release engineering work for the version available at ECLM 2013. A description of the [CHANGES] is included with the source. Upcoming in abcl-1.3.0: o per function call stack and memory exception handler in CL:COMPILE o further fixes in Quicklisp, q.v. [abcl-1.2.1]: http://abcl.org/releases/1.2.1 [CHANGES]: http://abcl.org/svn/tags/1.2.1/abcl/CHANGES

1 0

Re: [armedbear-devel] 20130823a Diffs for chemicalamba (Akka bridge in ABCL)
by Mark Evenson 08 Apr '15

08 Apr '15

On Aug 22, 2013, at 9:37 PM, ubikation _ <ubikation(a)gmail.com> wrote: > Hey Mark, > > I really appreciate your help but I am having trouble understand the diffs that you are sending me. I understand that HG is generating them but I am having trouble recreating your state. What tools do you recommend? I understand that creating a huge class isn't a good Java practice and I'm happy to break it up but it was hard for me to figure out exactly what goes where according to your diffs. […] For any software development, open or not, coming to terms with "diffs" is a basic skill that has no "right answer" for the tools one uses. A "diff" is a standardized format, used by a variety of tools including most IDEs these days. But in the beginning there was the command line, so the first tools you should come to terms with are diff(1) and patch(1): cmd$ [[[clone repo into "./chemicalambda"]]] cmd$ cd chemicalambda cmd$ patch -p 1 < file-that-contains-the-diff.diff The "-p 1" strips the top-level of the hierarchy, and then patch reads the contents of stdin for changes to make. One will see either success or error messages in applying the diff. Re-do until you get the results you want, then deal with the changes in your own version control ecology. What I like about hg is that one can just directly import a diff into the repo: cmd$ hg import file-that-contains-the-diff.diff but git certainly has similar functionality, somewhere. I avoided a comprehensive understanding diffs for many years, much to my own detriment.

1 0

[armedbear-devel] Unsubscribe
by Wayne Rogers 08 Apr '15

08 Apr '15

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

armedbear-devel