On September 8, 2004 04:34 pm, Dan Sugalski wrote: > At 11:02 PM +0100 9/8/04, Richard Jolly wrote: > >Hi, > > > ><newbie> > > > >Can someone provide clarification on what mixing languages will look > >like in practice, or point me to where its explained? > > It's not explained anywhere. Besides, it's syntax, and we don't do syntax. > :) > > It'll likely be something like: > > #! /usr/bin/perl > $foo = <<EOP > for foo in range(10): > print foo > EOP > $bar = eval $foo, "Python"; > > give or take. I doubt you'll see people mixing languages in source > files that often -- more likely you'll use library modules, and those > modules will be in perl 5 /perl 6/ python/ ruby/ tcl/ cola/ assembly/ > forth/ postscript/ befunge/ intercal/ applescript/ whatever.
Now why can't you use other languages symbols in your chosen language? They are all PMCs. It should "just work"(tm). Besides, that eval will either have to load the Python compiler (which may not exist) itself, or you "use" it prior... Still I think the libs should be cross language. If Parrot is built right, it should. (looks good so far ;)) If it won't work as of now, why won't it work? -- Thomas Fjellstrom [EMAIL PROTECTED] http://strangesoft.net
