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

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

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

Lisp compilation principles and SBCL internals

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

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

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

unfold-circular-list

Willem Broekema — 2009-11-28T09:18:23

There's a bug in unfold-circular-list, in that it calls subseq on a
circular list: subseq is defined as taking a "proper sequence". Below
is a patch.
- Willem

diff --git a/parse.lisp b/parse.lisp
index 4ee75b9..ab711b9 100644
--- a/parse.lisp
+++ b/parse.lisp
< at >< at > -46,7 +46,7 < at >< at >
     (loop for x on list as i upfrom 0
 as cdr-index = (find-cdr list (cdr x) i)
 until cdr-index
-finally (return (values (subseq list 0 (1+ i))
+finally (return (values (loop repeat (1+ i) collect (pop list))
 cdr-index)))))

 (defun symbol-package-fix-cl (symbol)

Filesystem question

Ram Vedam — 2009-11-27T04:16:27

compiling LiCE for Movitz

Ram Vedam — 2009-11-21T19:11:51

Build problem

2009-11-08T21:59:03

I am having problems building a Movitz image, with SBCL (and CMUCL) I
get the following error when compiling memref.lisp.

I can't see anything wrong with the code itself but it looks as if
an 'ECASE form within another one isn't being expanded properly.

There was a change to basic-macros.lisp in July, are there some other
diffs waiting to be committed ?

Robert Swindells

;; While Movitz compiling MEMREF in losp/muerte/memref.lisp:

debugger invoked on a COMMON-LISP:SIMPLE-ERROR:
  Don't know how to compile compound form ((HOST LITTLE)
                                           (MEMREF OBJECT OFFSET INDEX INDEX
                                            TYPE UNSIGNED-BYTE16 ENDIAN LITTLE
                                            PHYSICALP T))

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [RETRY-FUNOBJ      ] Retry compilation of MEMREF.
  1: [SKIP-TOPLEVEL-FORM] Skip the compilation of top-level form DEFUN MEMREF.

Movtiz License Idea - CC0

Jason Cady — 2009-10-16T10:32:04

Greetings,

There is a public domain style license called CC0 (Creative Common
Zero) that you might be interested in using for movitz related code.
It applies better to parts of the world that don't have a concept of
'public domain' & require jumping through several legal hoops to get a
similar effect, or even don't allow waiving of copyright.

If you choose CC0 for movitz stuff please, or explicitly reject it
please let me know.

Here are some links:
http://creativecommons.org/about/cc0
http://wiki.creativecommons.org/CC0_FAQ
http://creativecommons.org/publicdomain/zero/1.0/
http://creativecommons.org/choose/zero

I am making a new CC0 licensed termite
scheme/clojure/smalltalk/haskell/erlang style programming language
that I hope to make a CC0 licensed operating system with.