gmane.lisp.movitz.devel

Change Email

Steve Lefeber — 2012-12-02T18:47:18

Hello,

My current contact email is steve.lefeber< at >gmail.com.

I would like to change my contact information to slefeber1< at >elp.rr.com

Thank you.

v/r,
Steve Lefeber

Re: Macros

Frode V. Fjeld — 2011-01-31T19:32:56


Well, obviously the macro expander runs at compile-time, so any
functions it uses must also be available then. Have you tried wrapping
said functions in (eval-when (:compile-toplevel) ...) ?

Macros

2011-01-31T18:38:36

Is there anything special that needs to be done to add a macro to the system ?

I'm trying to add the COLLECT macro from CMUCL to Movitz as it is used by
the CMUCL pathnames code. The macro uses two helper functions which I am also
trying to add.

I have listed all three as members of the muerte package in
movitz/movitz/packages.lisp and tried building both with and without importing
the symbols into the movitz package.

Whatever I do Movitz complains that the helper functions are undeclared.

I started out with the three in a new file, but couldn't get Movitz to compile
it so have put them just before the pathnames code that should use them.

Robert Swindells

Re: What needs hacking?

Frode V. Fjeld — 2010-12-26T20:26:27


Well, these are not errors, but warnings? Do you see actual errors at
run-time?



I started importing simple-streams into Movitz, but never finished. I
guess some of the warnings are because of this.

Re: What needs hacking?

Krzysztof Drewniak — 2010-12-26T18:57:45

        WARNING:
           Function MUERTE.MOP:EXTRACT-LAMBDA-LIST is called (in
        "losp/muerte/los-closette.lisp") but not defined.
        WARNING:
           Function MUERTE::CANONICALIZE-SPECIALIZERS is called (in
        "losp/muerte/los-closette.lisp") but not defined.
        WARNING:
           Function MUERTE::PARSE-DEFMETHOD is called (in
        "losp/muerte/los-closette.lisp") but not defined.
        WARNING:
           Function MUERTE::CANONICALIZE-DEFGENERIC-OPTIONS is called
        (in "losp/muerte/los-closette.lisp") but not defined.
        WARNING:
           Function MUERTE::CANONICALIZE-DEFCLASS-OPTIONS is called (in
        "losp/muerte/los-closette.lisp") but not defined.
        WARNING:
           Function MUERTE::CANONICALIZE-DIRECT-SLOTS is called (in
        "losp/muerte/los-closette.lisp") but not defined.
        WARNING:
           Function MUERTE::CANONICALIZE-DIRECT-SUPERCLASSES is called
        (in "losp/muerte/los-closette.lisp") but not defined.

All spit out by a

Re: What needs hacking?

Frode V. Fjeld — 2010-12-26T16:50:18


Which functions, exactly?

As to the original question, I'm afraid Movitz is still in the stage
that "if you have to ask, you won't be able to do it". My best advice
would be to start it up and play with it, then ask questions if there's
something you can't get working or something you'd want to develop for
it.

Re: What needs hacking?

Krzysztof Drewniak — 2010-12-25T13:35:20

On Sat, 2010-12-25 at 03:49 +0100, Robert Strandh wrote: 
The functions defined in los-closette-compiler are not being used in
los-closette so there's undefined function errors in about 5 places.

Krzysztof Drewniak

Re: What needs hacking?

Krzysztof Drewniak — 2010-12-25T13:35:14

On Sat, 2010-12-25 at 03:49 +0100, Robert Strandh wrote: 
The functions defined in los-closette-compiler are not being used in
los-closette so there's undefined function errors in about 5 places.

Krzysztof Drewniak

Re: What need hacking?

Andreas Davour — 2010-12-25T09:42:01


Well, it depends on what you want it to be.

If you want to build a full OS, you'd need a project plan and a 
benevolent dictator to organize coding.

Otherwise, I think fixing the basic system (I don't think all of ANSI CL 
is implemented) and then making it possible to develop from within 
Movitz itself.

/andreas
--
"economics is a pseudoscience; the astrology of our time"
Kim Stanley Robinson

Re: What need hacking?

anon trol — 2010-12-25T07:06:51

has anyone tried loading movitz up on the various virtual machine platforms
(virtualbox in particular)?

Re: What needs hacking?

Robert Strandh — 2010-12-25T02:49:31

 > I just realized that CLOS is broken.

What do you mean?

Re: What needs hacking?

Krzysztof Drewniak — 2010-12-24T19:51:48

I just realized that CLOS is broken. (and that I typod in the subject)

What need hacking?

Krzysztof Drewniak — 2010-12-24T19:48:04

I'm not what you'd call an "experienced" coder, but I know some lisp and
can learn some x86 low-levelness if need be. I have looked around the
page and haven't been able to fixuge out what need doing, so if there's
anything that needs to get done, could y'all please provide some
pointers and I'll take a crack at it.

Krzysztof Drewniak

Re: loop

2010-09-09T19:53:21

[following up to a message from back in May]

Frode V. Fjeld wrote:

I think that there is a missing NIL block in loop but that isn't what
is causing the problem I'm seeing.

The code that I'm trying to compile uses a CLtL1 style loop syntax so
the block is created in LOOP-STANDARD-EXPANSION.

It basically does:

(loop
...
(return t)
...
(return nil))

I added some code to the compiler to print out what environments were
being searched when trying to compile the return/return-from forms. 

It seems as if a WITH-THINGS-ON-STACK-ENV is created in between the LOOP
and the second RETURN form, I'm guessing this was created to manage the
stack unwinding of the first RETURN, this is the environment used in the
the compilation of the second RETURN instead of the one belonging to the
enclosing LOOP special form.

Robert Swindells

Lisp compilation principles and SBCL internals

Semion Prihodko — 2010-08-18T12:50:42

Re: Booting LOS0 Failure

Burton Samograd — 2010-07-23T15:04:03

I tried building Movitz on a linux system using SBCL 1.0.29.11 and it
worked and ran fine.  I seem to remember that CLISP wouldn't even dump
the image properly in the past without crashing, so I guess there's
still some errors when using it to build movitz.


--
Burton Samograd

Booting LOS0 Failure

Burton Samograd — 2010-07-23T04:14:49

Hi,

I've been a bit interested in movitz again lately, so I downloaded the
git sources and compiled and dumped LOS0 using CLISP 2.48.  This all
went well, but when I tried to run the image I got the following:

http://imgur.com/A8Iwl

I tried looking through the code to see what happened, but the most I
could come up with was that maybe *all-process* was empty during the
call to (LIB::CURRENT-PROCESS).  Other than that I'm stumped.

Any idea what is happening?

--
Burton Samograd

Re: loop

2010-05-14T09:38:42

frode< at >netfonds.no wrote:

This feature was only added to the CMUCL version in 2008, I have tried
adding the same changes to the Movitz version but it still doesn't
work.

The code for LOOP is nearly the same in CMUCL, SBCL and CCL but there
are slight differences in each.

Robert Swindells

Re: loop

Frode V. Fjeld — 2010-05-14T07:09:57


The macro-expander for LOOP is copied pretty much verbatim from some
other implementation (perhaps CMUCL), so I'd be surprised if there's an
obvious problem like that. I'll have a look at it this evening,
hopefully.

loop

2010-05-12T16:46:33

The LOOP macro doesn't seem to create a NIL block.

I'm trying to add some code from CMUCL to Movitz that expects to be
able to (RETURN NIL) from within a LOOP.

I have tried comparing loop.lisp with the equivalents in CMUCL and
SBCL but can't see what is causing the problem.

Robert Swindells

Re: unfold-circular-list

Frode V. Fjeld — 2009-12-03T21:51:46


Just checked it in. Thanks!