Re: Storing Classes in Bytecode

2010-08-01 Thread Peter Lobsinger
On Fri, Jul 30, 2010 at 8:08 PM, Jonathan Worthington wrote: > chromatic wrote: >> >> Rakudo and other HLLs could greatly benefit from Parrot sorting out the >> "How and when do I declare a class?" mess.  The best way I can see for us to >> help them is to ease the requirement that all classes nee

Re: Memory needed to build Perl 6 on Parrot; problem, goal, incentive for solution

2010-08-01 Thread chromatic
On Sunday 01 August 2010 at 08:01, James E wrote: > Last week I successfully built Rakudo Star from source on two different > Linux/i386 machines, one real, one virtual. However, my attempt to > build Rakudo Star on my iBook was unsuccessful. It repeatedly failed at > this point: > >/Use

Re: Fwd: [svn:parrot] r48243 - trunk/runtime/parrot/library

2010-08-01 Thread Will Coleda
On Sun, Aug 1, 2010 at 2:46 AM, Patrick R. Michaud wrote: > On Sat, Jul 31, 2010 at 08:05:49PM -0400, Will Coleda wrote: >> Please a test to parrot to prevent someone else trying to speed up EMISSINGVERB. Whoops. >> rakudo inappropriately in the future. > > Test added in r48244. > > Pm Awesome,

Re: Memory needed to build Perl 6 on Parrot; problem, goal, incentive for solution

2010-08-01 Thread Andy Dougherty
On Sun, 1 Aug 2010, James E Keenan wrote: > 1. Problem. > > Last week I successfully built Rakudo Star from source on two different > Linux/i386 machines, one real, one virtual. However, my attempt to build > Rakudo Star on my iBook was unsuccessful. It repeatedly failed at this point: > >

Re: Memory needed to build Perl 6 on Parrot; problem, goal, incentive for solution

2010-08-01 Thread Daniel Arbelo
On Sun, Aug 1, 2010 at 12:01 PM, James E Keenan wrote: > In the course of discussion in that ticket, I noted that I had been able to > build Perl 6 on top of Parrot on that same machine at least as late as June > 2008, when I led a workshop to do that at YAPC::NA in Chicago. Coke > responded that

Memory needed to build Perl 6 on Parrot; problem, goal, incentive for solution

2010-08-01 Thread James E Keenan
1. Problem. Last week I successfully built Rakudo Star from source on two different Linux/i386 machines, one real, one virtual. However, my attempt to build Rakudo Star on my iBook was unsuccessful. It repeatedly failed at this point: /Users/jimk/work/rstar/rakudo-star-2010.07/install/b

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Nicholas Clark
On Sun, Aug 01, 2010 at 02:51:10PM +0100, Lucian Branescu wrote: > 2010/8/1 Alberto Simões : > > > > > > On 01/08/2010 14:34, Vasily Chekalkin wrote: > Does it have any disadvantage to set it from "#! perl" to > "#!/usr/bin/perl"? > > Also: "#! parrot"  ->  "#!/usr/bin/parrot" >

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Shawn H Corey
On 10-08-01 09:39 AM, Nicholas Clark wrote: I don't know for sure about Windows. I believe that interpreter choice is determined by looking up the extension in the registry, but I may well be wrong. (#! line and file permissions are not used) I haven't used Windows in a while but the last time

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Lucian Branescu
2010/8/1 Alberto Simões : > > > On 01/08/2010 14:34, Vasily Chekalkin wrote: Does it have any disadvantage to set it from "#! perl" to "#!/usr/bin/perl"? Also: "#! parrot"  ->  "#!/usr/bin/parrot" This is my favorite. >>> >>> Surely the #! for perl should be the path o

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Nicholas Clark
On Sun, Aug 01, 2010 at 11:34:34PM +1000, Vasily Chekalkin wrote: > >> Does it have any disadvantage to set it from "#! perl" to > >> "#!/usr/bin/perl"? > >> > >> Also: "#! parrot"  ->  "#!/usr/bin/parrot" > >> > >> This is my favorite. > > > > Surely the #! for perl should be the path of the perl

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Alberto Simões
On 01/08/2010 14:34, Vasily Chekalkin wrote: >>> Does it have any disadvantage to set it from "#! perl" to >>> "#!/usr/bin/perl"? >>> >>> Also: "#! parrot" -> "#!/usr/bin/parrot" >>> >>> This is my favorite. >> >> Surely the #! for perl should be the path of the perl used to run >> Configure.p

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Vasily Chekalkin
>> Does it have any disadvantage to set it from "#! perl" to >> "#!/usr/bin/perl"? >> >> Also: "#! parrot"  ->  "#!/usr/bin/parrot" >> >> This is my favorite. > > Surely the #! for perl should be the path of the perl used to run > Configure.pl, > and the #! for parrot be the path parrot will be in

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Nicholas Clark
On Sun, Aug 01, 2010 at 09:06:02AM +0200, Gerd Pokorra wrote: > Changing the first line of files which starts with "#! perl" would be > nice. > > Does it have any disadvantage to set it from "#! perl" to > "#!/usr/bin/perl"? > > Also: "#! parrot" -> "#!/usr/bin/parrot" > > This is my favorite

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread James E Keenan
Gerd Pokorra wrote: Changing the first line of files which starts with "#! perl" would be nice. Does it have any disadvantage to set it from "#! perl" to "#!/usr/bin/perl"? Also: "#! parrot" -> "#!/usr/bin/parrot"\\ I would oppose both of those. Whenever a new version of Perl 5 comes out

Re: Should we have programs with executable permissions in the distro

2010-08-01 Thread Gerd Pokorra
Changing the first line of files which starts with "#! perl" would be nice. Does it have any disadvantage to set it from "#! perl" to "#!/usr/bin/perl"? Also: "#! parrot" -> "#!/usr/bin/parrot" This is my favorite. Gerd Am Samstag, den 31.07.2010, 23:35 +0200 schrieb James E Keenan: > In