[armedbear-ticket] [armedbear] #32: Modify the currently disabled runtime-class.lisp code to not require ASM

armedbear armedbear-devel at common-lisp.net
Mon Mar 15 19:41:02 UTC 2010


#32: Modify the currently disabled runtime-class.lisp code to not require ASM
---------------------------+------------------------------------------------
  Reporter:  vvoutilainen  |       Owner:  somebody                                              
      Type:  enhancement   |      Status:  new                                                   
  Priority:  major         |   Milestone:  too-vague                                             
 Component:  other         |     Version:                                                        
Resolution:                |    Keywords:  jvm bytecode compiler runtime dynamic class generation
---------------------------+------------------------------------------------
Changes (by ehuelsmann):

  * milestone:  => too-vague


Old description:

> It's possible to define classes at runtime, by generating bytecode and
> loading it from the generated binary data, without ever writing it to a
> temporary file. runtime-class.lisp does that, but it requires an external
> bytecode library (ASM). ABCL has all the functionality for this to be
> done without ASM, so the task is to modify the runtime-class.lisp code so
> that ASM is no longer required and the code can be taken to be part of
> the build.

New description:

 It's possible to define classes at runtime, by generating bytecode and
 loading it from the generated binary data, without ever writing it to a
 temporary file. runtime-class.lisp does that, but it requires an external
 bytecode library (ASM). ABCL has all the functionality for this to be done
 without ASM, so the task is to modify the runtime-class.lisp code so that
 ASM is no longer required and the code can be taken to be part of the
 build.

--

Comment:

 We currently not-write to temporary files for any COMPILEd functions (ie
 this does not apply to COMPILE-FILE compiled functions - yet). So, the
 real requirement here is too vague.

 Do we need this for other purposes?

-- 
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/32#comment:1>
armedbear <http://common-lisp.net/project/armedbear>
armedbear


More information about the armedbear-ticket mailing list