Re: [Felix-language] micro-lisp implementation in felix

2006-12-20 Thread Erick Tryzelaar
skaller wrote: > On Tue, 2006-12-19 at 21:07 -0800, Erick Tryzelaar wrote: > > >>> Problem is import etc can be used for both importing >>> macros, but can also import other stuff .. hard to >>> know the difference. This needs revisiting. >>> >> is there another place we could open this u

Re: [Felix-language] micro-lisp implementation in felix

2006-12-19 Thread skaller
On Tue, 2006-12-19 at 21:07 -0800, Erick Tryzelaar wrote: > > Problem is import etc can be used for both importing > > macros, but can also import other stuff .. hard to > > know the difference. This needs revisiting. > > is there another place we could open this up for more opinions? Perhaps >

Re: [Felix-language] micro-lisp implementation in felix

2006-12-19 Thread skaller
On Tue, 2006-12-19 at 21:07 -0800, Erick Tryzelaar wrote: > skaller wrote: > >> These times are pretty disheartening. I can't imagine trying to work > >> with a 10k line felix program. > > > > Errmm .. but the problem here is g++ isn't it? > > Well sure, but we're generating code that make g++ v

Re: [Felix-language] micro-lisp implementation in felix

2006-12-19 Thread skaller
On Tue, 2006-12-19 at 21:07 -0800, Erick Tryzelaar wrote: > skaller wrote: > >> These times are pretty disheartening. I can't imagine trying to work > >> with a 10k line felix program. > > > > Errmm .. but the problem here is g++ isn't it? > > Well sure, but we're generating code that make g++ v

Re: [Felix-language] micro-lisp implementation in felix

2006-12-19 Thread Erick Tryzelaar
skaller wrote: >> These times are pretty disheartening. I can't imagine trying to work >> with a 10k line felix program. > > Errmm .. but the problem here is g++ isn't it? Well sure, but we're generating code that make g++ very unhappy. I guess things will be better whenever we get partial comp

Re: [Felix-language] micro-lisp implementation in felix

2006-12-19 Thread skaller
On Tue, 2006-12-19 at 02:32 -0800, Erick Tryzelaar wrote: > skaller wrote: > >> Oddly enough, it's gcc. > These times are pretty disheartening. I can't imagine trying to work > with a 10k line felix program. Errmm .. but the problem here is g++ isn't it? > It certainly would be interesting if

Re: [Felix-language] micro-lisp implementation in felix

2006-12-19 Thread Erick Tryzelaar
skaller wrote: >> Oddly enough, it's gcc. > > This is not odd. Gcc is a dog. What do you expect from an Open > Source project? Optimisation is particularly slow. > > However gcc 4.x does produce half way reasonable code. > It does do data flow analysis now, which is more than > Felix does. However

Re: [Felix-language] micro-lisp implementation in felix

2006-12-18 Thread skaller
On Mon, 2006-12-18 at 10:33 -0800, Erick Tryzelaar wrote: > skaller wrote: > > A parser should be fun to write .. and quite easy using the GLR parsing > > feature .. although lisp is rather trivial to parse .. and I guess > > you would probably use lisp to parse lisp .. :) > > > > Hmm, that would

Re: [Felix-language] micro-lisp implementation in felix

2006-12-18 Thread Erick Tryzelaar
skaller wrote: > On Mon, 2006-12-18 at 02:49 -0800, Erick Tryzelaar wrote: >> Hi everyone, >> >> I finally got around to implementing my port of the tiny lisp >> implementation from here: >> >> http://www.defmacro.org/ramblings/lisp-in-haskell.html >> >> It's pretty fun. While it doesn't actually

Re: [Felix-language] micro-lisp implementation in felix

2006-12-18 Thread skaller
On Mon, 2006-12-18 at 02:49 -0800, Erick Tryzelaar wrote: > Hi everyone, > > I finally got around to implementing my port of the tiny lisp > implementation from here: > > http://www.defmacro.org/ramblings/lisp-in-haskell.html > > It's pretty fun. While it doesn't actually parse syntax yet, A p

[Felix-language] micro-lisp implementation in felix

2006-12-18 Thread Erick Tryzelaar
Hi everyone, I finally got around to implementing my port of the tiny lisp implementation from here: http://www.defmacro.org/ramblings/lisp-in-haskell.html It's pretty fun. While it doesn't actually parse syntax yet, it does let you do this: //