Re: Perl6
On 12/28/05, Sastry <[EMAIL PROTECTED]> wrote: > I am looking for the latest Perl6 source code. Could somebody give me > a link to the same? > Do we need to install parrot before we install perl6? You can check out the latest code at: http://svn.openfoundry.org/pugs You'll need ghc-6.4 or later installed. Come to irc.freenode.net #perl6 if you need help building. Luke
Perl6
Hi I am looking for the latest Perl6 source code. Could somebody give me a link to the same? Do we need to install parrot before we install perl6? Thanks in advance Ravi Sastry
Re: Array/list transformations.
On Tue, Dec 27, 2005 at 01:13:10PM -0500, Rob Kinyon wrote: : On 12/27/05, Larry Wall <[EMAIL PROTECTED]> wrote: : > On Tue, Dec 27, 2005 at 12:10:45AM -0500, Rob Kinyon wrote: : > : Creating an array whose positions are aliases for positions in another : > : array can be useful. How about : > : : > : my @s := @a[0,2,4] is alias; : > : : > : @a[2] = 3; # @s[1] == 3 : > : @s[1] = 4; # @a[2] == 4 : > : : > : The default slicing behavior would default to "is copy", to preserve : > : the current semantics. Does that sound reasonable? : > : > Hmm. Assignment is already adequate for copying semantics. And binding : > the individual elements can presumably be done by: : > : > my [EMAIL PROTECTED] := @a[0,2,4]; : : What's the difference between: : : my @s := @a[0,2,4]; : : and : : my [EMAIL PROTECTED] := @a[0,2,4]; : : ? As with function parameter binding, the first would attempt to bind only the first argument, that is, @a[0]. The main difference between := and parameter binding is that := defaults to rw instead of readonly. Larry
Re: Cygwin versun plain XP (for working with Pugs+Parrot together)
In message <[EMAIL PROTECTED]>, jerry gay writes: : cygwin *should* compile parrot just fine. the last report i see on : http://smoke.parrotcode.org/smoke/ for i386-cygwin-gcc is from r10487, : which is a few weeks old, though. can any other cygwin users confirm : peter's report? there have been some significant changes to the config : system lately, these may have broken your platform. As of r10698, I get Checking MANIFEST.done. Setting up Configure's default values.done. Tweaking settings for miniparrot..done. Loading platform and local hints files..Missing right curly or square bracket at config/init/hints/cygwin.pm line 41, at end of line syntax error at config/init/hints/cygwin.pm line 41, at EOF Compilation failed in require at (eval 10) line 2. BEGIN failed--compilation aborted at (eval 10) line 2. The offending cygwin.pm looks to be truncated. Greg
Re: Cygwin versun plain XP (for working with Pugs+Parrot together)
It looks like it was just a missing curly brace. Fix commited as r10699. Thanks for reporting. -J -- On Tue, Dec 27, 2005 at 01:35:52PM -0600, Greg Bacon wrote: > In message <[EMAIL PROTECTED]>, > jerry gay writes: > > : cygwin *should* compile parrot just fine. the last report i see on > : http://smoke.parrotcode.org/smoke/ for i386-cygwin-gcc is from r10487, > : which is a few weeks old, though. can any other cygwin users confirm > : peter's report? there have been some significant changes to the config > : system lately, these may have broken your platform. > > As of r10698, I get > > Checking MANIFEST.done. > Setting up Configure's default values.done. > Tweaking settings for miniparrot..done. > Loading platform and local hints files..Missing right curly or square > bracket at config/init/hints/cygwin.pm line 41, at end of line > syntax error at config/init/hints/cygwin.pm line 41, at EOF > Compilation failed in require at (eval 10) line 2. > BEGIN failed--compilation aborted at (eval 10) line 2. > > The offending cygwin.pm looks to be truncated. > > Greg pgpIDTjRwiwNk.pgp Description: PGP signature
Re: Cygwin versun plain XP (for working with Pugs+Parrot together)
On 12/27/05, Peter Schwenn <[EMAIL PROTECTED]> wrote: > Dear Nick > > thanks. by the way how does one signal Pugs that Parrot is to be used > "Externally".? Although I've played with pugs for a few hours, it was on Linux, and I didn't get around to investigating the backends (especially as the parrot one sounded like the least functional at the time). Hopefully someone else can advise... Nick
Re: Cygwin versun plain XP (for working with Pugs+Parrot together)
Dear Nick thanks. by the way how does one signal Pugs that Parrot is to be used "Externally".? Nick Glencross wrote: On 12/26/05, jerry gay <[EMAIL PROTECTED]> wrote: cygwin *should* compile parrot just fine. the last report i see on http://smoke.parrotcode.org/smoke/ for i386-cygwin-gcc is from r10487, which is a few weeks old, though. can any other cygwin users confirm peter's report? there have been some significant changes to the config system lately, these may have broken your platform. The core parrot VM builds on cygwin, but dynclasses don't link. To help the build along, a quick hack such as 'echo all: > src/dynclasses/Makefile' can help it along. dynclasses are nice, but don't prevent parrot being pretty functional on cygwin. As such, we might want to skip that part of the build until this is sorted. ... OR work to make Cygwin work (e.g. to Configure.pl Parrot's Makefile) if it's failing in cygwin, this is the best fix. I've been revisiting the cygwin build a few times over the last year to see if I can get dynclasses working, and I can't see an alternative to building libparrot as a DLL, linking the dynclasses against this DLL (or a .dll.a stub) and a smalish tweak to the config_string functionality. We've currenly got: Cygwin build parent https://rt.perl.org/rt3/Ticket/Display.html?id=36540 dynclasses are not builidng on Cygwin https://rt.perl.org/rt3/Ticket/Display.html?id=36836 Relaxing parrot dependency on parrot_config https://rt.perl.org/rt3/Ticket/Display.html?id=37303 (The patch has regressed after recent changes) There's also a thread "Better support for libparrot.so" which will allow the libparrot.dll to be built cleanly on cygwin This code isn't yet associated with any particular bug Nick
Re: Array/list transformations.
On 12/27/05, Larry Wall <[EMAIL PROTECTED]> wrote: > On Tue, Dec 27, 2005 at 12:10:45AM -0500, Rob Kinyon wrote: > : Creating an array whose positions are aliases for positions in another > : array can be useful. How about > : > : my @s := @a[0,2,4] is alias; > : > : @a[2] = 3; # @s[1] == 3 > : @s[1] = 4; # @a[2] == 4 > : > : The default slicing behavior would default to "is copy", to preserve > : the current semantics. Does that sound reasonable? > > Hmm. Assignment is already adequate for copying semantics. And binding > the individual elements can presumably be done by: > > my [EMAIL PROTECTED] := @a[0,2,4]; What's the difference between: my @s := @a[0,2,4]; and my [EMAIL PROTECTED] := @a[0,2,4]; ? Rob
Journal moved.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is just a heads-up for people tracking my use.perl.org journal -- the Pugs journal is now moved to http://pugs.blogs.com/. I'd like to thank to Six Apart for their kind offer in sponsoring the hosting. I'm slowly catching up writing about new developments in the last couple of months, eg. the new Perl6 Rules implementation in Perl6 and Haskell, PIL^N runtime for the object model, JIB/Sixpan, Perl6::Doc, and module interface semantics. I am not sure how much (if any) of this should be cross-posted to P6C... Would the list subscribers be interested in getting them in email form, in addition to the current blog format? Thanks, Audrey -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDsXSntLPdNzw1AaARAhCKAJ9yaEGBxjfOiIoAV+yaAE41abNdngCeLjRv R6LNGPYOFGU1dIj60nhpyAY= =/tX1 -END PGP SIGNATURE-
Re: Cygwin versun plain XP (for working with Pugs+Parrot together)
On 12/26/05, jerry gay <[EMAIL PROTECTED]> wrote: > cygwin *should* compile parrot just fine. the last report i see on > http://smoke.parrotcode.org/smoke/ for i386-cygwin-gcc is from r10487, > which is a few weeks old, though. can any other cygwin users confirm > peter's report? there have been some significant changes to the config > system lately, these may have broken your platform. The core parrot VM builds on cygwin, but dynclasses don't link. To help the build along, a quick hack such as 'echo all: > src/dynclasses/Makefile' can help it along. dynclasses are nice, but don't prevent parrot being pretty functional on cygwin. As such, we might want to skip that part of the build until this is sorted. >> ... >> > > OR > > > > work to make Cygwin work (e.g. to Configure.pl Parrot's Makefile) > > > if it's failing in cygwin, this is the best fix. I've been revisiting the cygwin build a few times over the last year to see if I can get dynclasses working, and I can't see an alternative to building libparrot as a DLL, linking the dynclasses against this DLL (or a .dll.a stub) and a smalish tweak to the config_string functionality. We've currenly got: Cygwin build parent https://rt.perl.org/rt3/Ticket/Display.html?id=36540 dynclasses are not builidng on Cygwin https://rt.perl.org/rt3/Ticket/Display.html?id=36836 Relaxing parrot dependency on parrot_config https://rt.perl.org/rt3/Ticket/Display.html?id=37303 (The patch has regressed after recent changes) There's also a thread "Better support for libparrot.so" which will allow the libparrot.dll to be built cleanly on cygwin This code isn't yet associated with any particular bug Nick
[perl #37935] [TODO] build - CLI options to step passing
CLI options are now accessed from a Parrot::Configure::Data object contained by the Parrot::Configure object that is now passed to every step as the first paramter. Implimented in a 'large number' of changesets between r10566 and r10658. -J --
