Re: Compiling to Parrot

[Dan Sugalski]

At 5:48 PM +0100 1/21/03, K Stol wrote:

Is it possible for parrot-code to call functions in other parrot files?
(which implies there is some program which consists of multiple files)

Oh, absolutely.

What one generally does is load in other bytecode files. Those files, on loading, will install a variety of symbols into the interpreter's global pool, at which point you can use them as you need to.

This is, generally speaking, a dynamic linking scheme, rather than the more traditional static link that resolves symbols and such, as we're dealing with a much more dynamic environment.

----- Original Message -----
From: "Dan Sugalski" <[EMAIL PROTECTED]>
To: "K Stol" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, January 21, 2003 5:20 PM
Subject: Re: Compiling to Parrot

 At 5:13 PM +0100 1/21/03, K Stol wrote:
 >Only thing I need to know before I can start is: what would the purpose

be

 >of a Lua to Parrot compiler? Lua is originally an embedded language for
 >easy-scripting, as far as I understand. How could it be used when

targeted

 >to parrot? Would it be possible to call functions written in Lua (and

which

 >are then compiled to parrot) from (for example) a python script? (So:

python

 >script calls function writtenin Lua and compiled to parrot).

 If you follow the calling conventions, then yes you'll be able to
 call python/ruby/perl/befunge routines from Lua code, and vice versa.

 >From: "Dan Sugalski" <[EMAIL PROTECTED]>
 >  > At 5:01 PM +0100 1/21/03, K Stol wrote:
 >>  >well, I think not, then I can't help it. What do you think about
 >compiling
 >>  >Lua to parrot (IMCC)?
 >>
 >>  I like the idea, and I don't think you'll see anyone else tackle it
 >>  for a while. (And if that falls through, there's always LISP... :)
 >>
 >>  >From: "Dan Sugalski" <[EMAIL PROTECTED]>
 >>  >  > At 4:46 PM +0100 1/21/03, K Stol wrote:
 >>  >>  >Well, I'd do it as a project for my Bachelor's, so I won't get
 >permission
 >>  >to
 >>  >>  >do such a project, if it already exists.
 >>  >>
 >>  >>  Ah, that could be a problem. Will it be a problem if you start a
 >>  >>  project that someone else later also starts?
 >>  >>
 >>  >>  >From: "Dan Sugalski" <[EMAIL PROTECTED]>
 >>  >>  >  > At 9:17 AM +0100 1/21/03, K Stol wrote:
 >>  >>  >>  >Hi there,
 >>  >>  >>  >
 >>  >>  >>  >A few weeks ago I posted something about a Tcl->parrot

compiler,

 >but
 >>  >>  >>  >Will Coleda already was working on such a project. It would

be a

 >as
 >>  >>  >>  >a final project for my bachelor's. But because such already
 >exists,
 >>  >>  >>  >I'm looking for something else.
 >>  >>  >>
 >>  >>  >>  If you're interested in doing a Tcl compiler, by all means, go
 >>  >>  >>  ahead--I wouldn't let the fact that someone else is doing it

stop

 >>  >>  >>  you. The point of doing it is for the experience, which you'll

get

 >>  >>  >>  regardless of any other implementation. It's also distinctly
 >possible
 >>  >>  >>  that neither you nor Will will finish a full implementation

(as

 >it's
 >>  >>  >>  likely a rather large undertaking for one person) but you'll

each
 > >>  >  > >  > have part of it that can be merged together.

--
                                        Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk