Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread Matthias Felleisen
On Mar 4, 2013, at 10:35 AM, mikel evins wrote: > Besides the practical reasons I already gave, I also think that there's been > a gradual trend away from image-based development over the last twenty years, > and I think it's regrettable. I'm not saying it's the greatest thing since > sliced b

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread mikel evins
On Mar 4, 2013, at 12:01 PM, Jens Axel Søgaard wrote: > Hi Mikel, > > You projects sounds very interesting. > > 2013/3/4 mikel evins : >> Oh, except for the case where I want to deploy on iOS, which forbids JIT. >> >> Of course, Racket doesn't deliver on iOS anyway, as far as I know, except

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread Jens Axel Søgaard
Hi Mikel, You projects sounds very interesting. 2013/3/4 mikel evins : > Oh, except for the case where I want to deploy on iOS, which forbids JIT. > > Of course, Racket doesn't deliver on iOS anyway, as far as I know, except > through > the expedient of compiling to Javascript (which may be adeq

Re: [racket-dev] Extflonum type for windows

2013-03-04 Thread Matthew Flatt
Great! This all looks like the right idea, and I'll take a closer look as soon as possible, but maybe not until the end of the week. At Mon, 4 Mar 2013 19:06:32 +0300, Michael Filonenko wrote: > Hello all, > > The following pull request provides long double type (extflonum) on > win32: https://gi

[racket-dev] Extflonum type for windows

2013-03-04 Thread Michael Filonenko
Hello all, The following pull request provides long double type (extflonum) on win32: https://github.com/plt/racket/pull/265 Extflonum arithmetic is implemented in a set of functions compiled into longdouble.dll (dll and lib attached, source code included in the pull request). It has been compile

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread mikel evins
On Mar 4, 2013, at 9:56 AM, mikel evins wrote: > > On Mar 4, 2013, at 9:54 AM, Matthew Flatt wrote: > >> At Mon, 04 Mar 2013 09:35:42 -0600, mikel evins wrote: >>> The reason I ask is that MacScheme made it easy to have most of an app >>> compiled to bytecode, which was very compact and reas

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread mikel evins
On Mar 4, 2013, at 9:54 AM, Matthew Flatt wrote: > At Mon, 04 Mar 2013 09:35:42 -0600, mikel evins wrote: >> The reason I ask is that MacScheme made it easy to have most of an app >> compiled to bytecode, which was very compact and reasonably efficient, but >> to >> optionally and selectively

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread Matthew Flatt
At Mon, 04 Mar 2013 09:35:42 -0600, mikel evins wrote: > The reason I ask is that MacScheme made it easy to have most of an app > compiled to bytecode, which was very compact and reasonably efficient, but to > optionally and selectively compile performance-critical procedures to native > code. [

Re: [racket-dev] [plt] Push #26313: master branch updated

2013-03-04 Thread Matthew Flatt
At Mon, 4 Mar 2013 06:30:35 -0700, Jay McCarthy wrote: > 2d5884b broke some of my Scribble documents. Repair pushed. _ Racket Developers list: http://lists.racket-lang.org/dev

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread mikel evins
On Mar 4, 2013, at 9:22 AM, Matthew Flatt wrote: > At Mon, 04 Mar 2013 08:50:19 -0600, mikel evins wrote: >> Is the bytecode format platform-independent? > > Yes. > >> Is it documented? I guess I probably won't need to know gory details >> about the bytecode format, but I could be wrong. > >

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread Matthew Flatt
At Mon, 04 Mar 2013 08:50:19 -0600, mikel evins wrote: > Is the bytecode format platform-independent? Yes. > Is it documented? I guess I probably won't need to know gory details > about the bytecode format, but I could be wrong. The gory encoding details are not documented, but the documentation

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread mikel evins
On Mar 4, 2013, at 8:09 AM, Matthew Flatt wrote: > At Sat, 02 Mar 2013 08:44:38 -0600, mikel evins wrote: >> I'm working on a Lisp. Recently I've been tinkering with an implementation >> in >> Racket. Racket makes it impressively easy to write. >> >> I need it ultimately to be an old-fashione

Re: [racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread Matthew Flatt
At Sat, 02 Mar 2013 08:44:38 -0600, mikel evins wrote: > I'm working on a Lisp. Recently I've been tinkering with an implementation in > Racket. Racket makes it impressively easy to write. > > I need it ultimately to be an old-fashioned kernel+image Lisp, with a > platform-specific kernel execut

Re: [racket-dev] [plt] Push #26313: master branch updated

2013-03-04 Thread Matthew Flatt
At Mon, 4 Mar 2013 06:30:35 -0700, Jay McCarthy wrote: > 2d5884b broke some of my Scribble documents. > > [...] > > I can link you to the full code, but it is a section (created by > @title) with the 'toc and 'unnumbered styles. It generates this page: > > http://jeapostrophe.github.com/archive.

Re: [racket-dev] [plt] Push #26313: master branch updated

2013-03-04 Thread Jay McCarthy
2d5884b broke some of my Scribble documents. The test that you removed previously failed, so the "on this page" list was blank, but now I get this error: cdr: contract violation expected: pair? given: '() context...: /home/jay/Dev/scm/plt/collects/scribble/html-render.rkt:531:4: render-o

[racket-dev] using Racket to build an image-based Lisp: feasible?

2013-03-04 Thread mikel evins
I'm working on a Lisp. Recently I've been tinkering with an implementation in Racket. Racket makes it impressively easy to write. I need it ultimately to be an old-fashioned kernel+image Lisp, with a platform-specific kernel executable and a platform-independent heap image. I'm aware that's no