Re: [Kawa-commonlisp-dev] [GSoC] Status

[Jamison Hope]

On Aug 6, 2012, at 1:37 PM, Charles Turner wrote:

> Done:
> * Basic type declarations
> * Symbols (mostly complete, just some spurious printing problems)
> * Packages - mostly complete, still unimplemented:
> ;;*modules*
> ;;provide
> ;;rename-package
> ;;require
> ;;do-all-symbols
> ;;do-external-symbols
> ;;do-symbols
> ;;unexport
> ;;find-all-symbols
> * Destructuring bind

Great work!

> Currently:
> * Expanding the testsuite for the features I've implemented with help
> from the Sacla project.

Scala, right? Or are you just eating lots of pasta as you work on the
tests? ;-)

Either way, yay testsuite expansion.

> * Freakin' out over the bootstrapping problems.

This is about your commenting/uncommenting loadClass("defmacro") bit,  
right?

Does that loadClass line need to be there at all, or could we just have
some lines like defSntxStFld("destructuring-bind",  
"gnu.commonlisp.lisp.defmacro");
instead?

My understanding of how those things work is this:
- loadClass() immediately loads everything in the file
- def*Fld() doesn't load anything yet, it just lazily says where to  
find the
function/macro later; it gets loaded as if by
(import (only (class name) function-name))
the first time the function is referenced.

If we use loadClass(), then the order of the statements matters; if we  
use
def*Fld(), then order doesn't matter because the prerequisites will also
be lazily loaded as needed.

Per, please correct those statements.

> * Considering how best to approach CL sequences with the existing Kawa
> infrastructure.

Can you elaborate, please? We briefly discussed this a long time ago
(pretty sure it was before GSOC 2012 started) but I don't remember what
the issues were.


Jamie

--
Jamison Hope
The PTR Group
www.theptrgroup.com