Re: Guile Lua

2013-01-14 Thread Ian Price
Stefan Israelsson Tampe writes: > To note is that in order to implement common lisp one need to bypass tree-il > and generate directly to glil, the reason is that tagbody is poorly > represented > by tree-il. If we intend to be multilingual it would be nice to be able to > effectively > represent

Re: Guile Lua

2013-01-14 Thread Stefan Israelsson Tampe
Hi, To note is that in order to implement common lisp one need to bypass tree-il and generate directly to glil, the reason is that tagbody is poorly represented by tree-il. If we intend to be multilingual it would be nice to be able to effectively represent those ideoms. Any thoughts on it? /Stef

Re: Guile Lua

2013-01-13 Thread Ian Price
Nala Ginrut writes: >> What about common lisp is scheme a lisp or is CL a scheme :-) >> > > IIRC, someone raised the topic that emerge Clisp into Guile in 2011, > but what's the status now? > >> Anyway to support CL I would think that we need to support placing >> properties >> on symbols, e,g.

Re: Guile Lua

2013-01-12 Thread Nala Ginrut
On Sat, 2013-01-12 at 09:37 -0500, Noah Lavine wrote: > I sent an email about that, but it was only an idea. I thought it > would be nice if we could work with the Clisp people. However, I can > see some barriers to actually doing that, and I don't intend to work > on it any time soon. > Thanks fo

Re: Guile Lua

2013-01-12 Thread Noah Lavine
I sent an email about that, but it was only an idea. I thought it would be nice if we could work with the Clisp people. However, I can see some barriers to actually doing that, and I don't intend to work on it any time soon. Noah On Sat, Jan 12, 2013 at 3:43 AM, Nala Ginrut wrote: > On Wed, 20

Re: Guile Lua

2013-01-12 Thread Nala Ginrut
On Wed, 2012-11-21 at 16:51 +0100, Stefan Israelsson Tampe wrote: > Hi, > > In terms of strategy, I think Guile’s focus should remain primarily > on > > Scheme variants, and ELisp. Other language front-ends are of course > > welcome, but we must keep an eye on what the demand is. > > What about c

Re: Guile Lua

2012-11-22 Thread nalaginrut
On Wed, 2012-11-21 at 14:25 +0100, Ludovic Courtès wrote: > Hi! > > nalaginrut skribis: > > > I switch to lua branch then compiled it and try, seems some bugs there, > > it can't run successfully: > > ---cut > > scheme@(guile-user)> ,L lua > > Happy hacking wi

Re: Guile Lua

2012-11-21 Thread Stefan Israelsson Tampe
Hi, > In terms of strategy, I think Guile’s focus should remain primarily on > Scheme variants, and ELisp. Other language front-ends are of course > welcome, but we must keep an eye on what the demand is. What about common lisp is scheme a lisp or is CL a scheme :-) Anyway to support CL I would

Re: Guile Lua

2012-11-21 Thread Ludovic Courtès
Hi! nalaginrut skribis: > I switch to lua branch then compiled it and try, seems some bugs there, > it can't run successfully: > ---cut > scheme@(guile-user)> ,L lua > Happy hacking with Lua! To switch back, type `,L scheme'. > lua@(guile-user)> x=1 Maybe yo

Re: Guile Lua

2012-11-20 Thread nalaginrut
On Mon, 2012-11-19 at 22:07 +0100, Ludovic Courtès wrote: > Hi! > > nalaginrut skribis: > > > I'd like to know what work should the maintainer take? As I know there's > > some work has been done, but it didn't merge into stable-2.0. What's the > > rest work? Does it work now? > > I think the f

Re: Guile Lua

2012-11-20 Thread nalaginrut
On Tue, 2012-11-20 at 18:04 +0100, Ludovic Courtès wrote: > Hi! > > nalaginrut skribis: > > > @ludo: Thanks! I'll try to do it follow your steps. > > Besides, do we have the final conclusion for the multi-lang choosing > > approach, say, --lang=lua/elisp or #

Re: Guile Lua

2012-11-20 Thread Ludovic Courtès
Hi! nalaginrut skribis: > @ludo: Thanks! I'll try to do it follow your steps. > Besides, do we have the final conclusion for the multi-lang choosing > approach, say, --lang=lua/elisp or #lang lua or a script: > guile-lua/guile-elisp... whatever. IIRC, ijp raised such a topic,

Re: Guile Lua

2012-11-20 Thread Ian Price
nalaginrut writes: > Besides, do we have the final conclusion for the multi-lang choosing > approach, say, --lang=lua/elisp or #lang lua or a script: > guile-lua/guile-elisp... whatever. IIRC, ijp raised such a topic, but it > seems no conclusion. No, I started compiling a list of t

Re: Guile Lua

2012-11-19 Thread Daniel Hartwig
On 20 November 2012 08:24, Ian Price wrote: > I'm no expert on lua, so I can't give you a huge long list, but Phil did > make a post titled "Creating a Lua Roadmap" at > http://article.gmane.org/gmane.lisp.guile.devel/12291 > > The first issues would be them. There appears to be a notes.org in the

Re: Guile Lua

2012-11-19 Thread nalaginrut
> When all this is in place, we can consider merging the branch. I > wouldn’t want to merge a half-baked front-end. > > WDYT? > > Ludo’. > > @ijp: thanks for the info ;-) @ludo: Thanks! I'll try to do it follow your steps. Besides, do we have the final conclusion for

Re: Guile Lua

2012-11-19 Thread Ian Price
nalaginrut writes: > I'm interested on our multi-language feature. And I wish Guile become > the real dynamic language compiler collection someday, which mean we > need to add more workable languages. > I'd like to know what work should the maintainer take? As I know there's > some work has been

Re: Guile Lua

2012-11-19 Thread Ludovic Courtès
Hi! nalaginrut skribis: > I'd like to know what work should the maintainer take? As I know there's > some work has been done, but it didn't merge into stable-2.0. What's the > rest work? Does it work now? I think the first task for you (congratulations! ;-)) or anyone else interested will be t

Re: Guile Lua

2012-11-18 Thread nalaginrut
On Sat, 2012-11-17 at 16:30 +, Ian Price wrote: > About two weeks ago, I emailed "Phil", who had shown some interest in > hacking guile lua a while back. I still haven't heard back from him, nor > has that branch been touched in 18 months, so I think we can sa

Guile Lua

2012-11-17 Thread Ian Price
About two weeks ago, I emailed "Phil", who had shown some interest in hacking guile lua a while back. I still haven't heard back from him, nor has that branch been touched in 18 months, so I think we can safely say we need a new maintainer for it. I have little knowledge of