Get Involved With Pugs

Replies are listed 'Best First'.
Re: Get Involved With Pugs by Juerd (Abbot) on May 11, 2005 at 13:33 UTC
A short guide to adding tests is in order, because if you report a bug, the standard reply will be "write a test for it". There's currently a bug in Pugs that makes array references flatten in list context. A bug test is simple: write what you did and what you expected first: `# What I did my @foo; push @foo, []; # What I expected @foo.elems == 1 # But I got @foo.elems == 0` [download] Then, rewrite the expectation as a test: `ok(@foo.elems == 1, "\@foo has 1 element");` [download] If you're dealing with comparison, it's better to use is() instead of ok(), because you then get extra debugging output: `is(@foo.elems, 1, "\@foo has 1 element");` [download] Add enough stuff to make it a script (the "plan" is the number of tests in the test script), and make sure you're loading the Test module: `#!/usr/bin/pugs use v6; use Test; plan 1; my @foo; push @foo, []; is(@foo.elems, 1, "\@foo has 1 element");` [download] And then report your bug-report-test to a pugs developer, so that it can be included in the test suite. It'll remain there for a long time, to make sure that the bug, once fixed, won't come back (regress). If you have write access in the repository, commit the test as pugs/t/pugsbugs/foo.t, where foo is descriptive (in this case, the test is in flattening.t). If you will be reporting multiple bugs, request committer access from Autrijus. Giving you access once is easier than copying and pasting every bug report test. Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }	[reply] [d/l] [select]
Re^2: Get Involved With Pugs by audreyt (Hermit) on May 11, 2005 at 16:32 UTC
Incidentally, less than 24 hours after the test case has been written, this issue has been addressed -- and raising an important corner case in Perl 6's design. :-)	[reply]
Re: Get Involved With Pugs by brian_d_foy (Abbot) on May 11, 2005 at 18:40 UTC
On the advocacy side, I would love to have a regular Pugs column in The Perl Review, along with other articles about Pugs and Perl 6 or Parrot. Frank Antonsen has been writing about functional programming, and has another article on parsing in the next issue, too. They aren't directly about Pugs or Haskell, but they talk about the change in mindset and perspective, and how you do things such as creating Pugs. :) -- brian d foy <brian@stonehenge.com>	[reply]
Re: Get Involved With Pugs by revdiablo (Prior) on May 11, 2005 at 17:30 UTC
Ask for a feature ... Write p6 tests It might also be helpful to point out that in #perl6 land, these two ideas usually go hand in hand. As Juerd says, the standard reply to a bug report is usually, "where's the test?" The standard reply to a feature request is usually the same. I believe the succinct way to say it is that autrijus trades implementation for tests. :-)	[reply]
Re^2: Get Involved With Pugs by adrianh (Chancellor) on May 12, 2005 at 18:01 UTC
I believe the succinct way to say it is that autrijus trades implementation for tests. :-) That is such a nice way to talk about TDD. I will have to steal it :-)	[reply]
Re: Get Involved With Pugs by tphyahoo (Vicar) on May 11, 2005 at 16:32 UTC
Who can get involved with PUGS is determined first, by what systems PUGS can be installed on. The Pugs Readme gives instructions on installing but doesn't say what systems PUGS is known/believed to be installable. Does such a list exist anywhere? Has anyone been able to get this to install on a windows box, which is what I have?	[reply]
Re^2: Get Involved With Pugs by Limbic~Region (Chancellor) on May 11, 2005 at 16:45 UTC
tphyahoo, Pugs should work on every platform that GHC works on. There are a fair amount of binary packages to include Win32. More information can be found here. Cheers - L~R	[reply]
Re^3: Get Involved With Pugs by stefp (Vicar) on May 14, 2005 at 04:19 UTC
ghc is available as a rpm for Mandriva. This packaging has been contributed by Rafael Garcia-Suarez. -- stefp	[reply]
Re^2: Get Involved With Pugs by tphyahoo (Vicar) on May 12, 2005 at 08:40 UTC
Thanks, Limbic~Region. PUGS on MS Windows looks like a good place to start if you want PUGS to play with Windows and ActiveState. Monastery post Hello Perl 6. Running pugs on Windows makes me pretty optimistic as well :) FWIW, the binary windows installer for GHC. Secondly, GHC Contributors indicates that GHC works with windows targetting mingw and cygwin. I seem to recall a chatterbox interaction the upshot of which was that getting PUGS to install on Cygwin was less than trivial, which come to think of it is what prompted me to ask whether PUGS could be installed on a windows box. Maybe this was a red herring though and I don't even need cygwin... I just downloaded GHC for windows and will see if I can get PUGS onto my win box today, without cygwin. If anyone else has light to shed about this, would be great :)	[reply]
Re^3: Get Involved With Pugs by Corion (Patriarch) on May 12, 2005 at 08:46 UTC
The "GHC for cygwin" is a misnomer, as GHC is mostly a native Win32 application. I haven't seen which backend for code generation GHC actually uses, but I assume it is built-in. I don't know if there is a build of GHC with MSVC, but as GHC is a compiler itself, I assume that GHC is compiled with itself mostly. I am developing Pugs on Win32 without any problems, because the support of GHC for Win32 is really good and one can easily access the Win32 API from within GHC. There are some things that are different between Pugs/Win32 and Pugs/POSIX: `fork()` will not happen, or it will be the ugly abomination that fork emulation is under Perl5 `system()` and built-in threading (`async` blocks) don't play together. This might be fixed by making GHC spawn OS threads when launching a `system()` command, so the rest of Pugs continues running. `select()` on non-sockets - `WaitForSingleObject` cannot wait for `winsock.dll` objects, and the `select` call of winsock does not know about the other kernel objects.	[reply]
Re^4: Get Involved With Pugs by tphyahoo (Vicar) on May 12, 2005 at 08:50 UTC
Re^5: Get Involved With Pugs by Corion (Patriarch) on May 12, 2005 at 08:55 UTC
Re: Get Involved With Pugs by polettix (Vicar) on May 18, 2005 at 10:07 UTC
One of things I were afraid of was that I did not understand the entire architecture very well - Pugs, Parrot, Ponie, Perl6... any more? But that was the dark side of lazyness, so I decided it was time to rise and see what has to be done. At the moment, I've been able to install it inside a user-space directory, which doesn't "clutter" the pseudo-production system I live in. I thought that it could be good to share this with you all, even if it's something that applies only here-and-now; just to take people lazier than me on the boat :) My procedure in Linux (Slackware, so no rpm-s or similars): Haskell is the first step. As of yesterday, version 6.4 is the latest available, so I link it here for your convenience. I appreciated the possibility to `make in-place` and avoid installing the package in a different place. downloaded http://haskell.org/ghc/dist/6.4/ghc-6.4-i386-unknown-linux.tar.bz2 expanded into `$HOME/src/ghc-6.4` `cd $HOME/src/ghc-6.4 ./configure make in-place PATH="$PATH:$HOME/src/ghc-6.4/bin/i386-unknown-linux"` [download] I actually added the last line to `$HOME/.bashrc` as well (I don't still plan to use it inside crontab jobs :) Pugs README says that you need an additional library to do something that's obscure for me at the moment. But I wanted all whistles and bells, so I installed it as well: downloaded ftp://ftp.cse.unsw.edu.au/pub/users/dons/hs-plugins/snapshots/hs-plugins-20050501.tar.gz expanded into `$HOME/src/ghc-6.4/hs-plugins-20050501` `cd $HOME/src/ghc-6.4/hs-plugins-20050501 ./configure --prefix="$HOME/src/ghc-6.4/hs-plugins" make make install make register` [download] The last line is quite important, because it registers the library inside Haskell. I presume. Time for Parrot now. For what I understood, it's the foundation floor for all the Perl 6 stuff, so I decided to install it before the other floors :) downloaded http://search.cpan.org/CPAN/authors/id/L/LT/LTOETSCH/parrot-0.2.0.tar.gz expanded into `$HOME/src/parrot-0.2.0` `perl Configure.pl --prefix="$HOME/sviluppo/parrot-0.2.0" make make test # make install` [download] Yes, last line is commented out. Which basically makes the `prefix` quite unuseful. Why? I don't know exactly, but it seems that Pugs feels more comfortable with the source tree of Parrot instead of the installed version - I had to fight with various errors in Pugs installation process before the light switched on. Good for me that I paid my dues to the local energy company. `export PUGS_EMBED=parrot #export PARROT_PATH="$HOME/sviluppo/parrot-0.2.0" export PARROT_PATH="$HOME/src/parrot-0.2.0"` [download] These variables are needed for the following Pugs installation process. I decided to report all my installation process, so I report one more commented line, just to stress that the following Pugs installation process expects the path to the Parrot compilation directory instead of the installation one. Pugs, at last! The previous setup (HS library, environment variables) gets rid of scary messages about being forced to do thing manually... downloaded http://search.cpan.org/CPAN/authors/id/A/AU/AUTRIJUS/Perl6-Pugs-6.2.3.tar.gz expanded into `$HOME/src/Perl6-Pugs-6.2.3` `PUGSINSTALL="$HOME/sviluppo/pugs-6.2.3" perl Makefile.PL PREFIX="$PUGSINSTALL" DESTDIR="$PUGSINSTALL" make make test make install PATH="$PATH:$PUGSINSTALL/bin"` [download] Yes, I admit my ignorance, I really don't know the difference between `PREFIX` and `DESTDIR`, but without the latter the installation inside my home directory tree did not work :) The whole process requires some compiling but should go quite smooth; in about 1 hour you'd have pugs at your fingertips and start playing with hangman (in `$HOME/src/Perl6-Pugs-6.2.3/examples/games`), at last! Flavio (perl -e 'print(scalar(reverse("\nti.xittelop\@oivalf")))') Don't fool yourself.	[reply] [d/l] [select]
Re: Get Involved With Pugs by tphyahoo (Vicar) on May 12, 2005 at 11:05 UTC
`pugs -e "{ 'Hello, ', @^x }.('World!').say"` [download] :) It took me about two hours to track down, install, and run "hello world" on pugs on windows. Now what? Look for something to do? Or slink off and wait? :)	[reply] [d/l]
Re^2: Get Involved With Pugs by revdiablo (Prior) on May 12, 2005 at 16:46 UTC
Now what? Out of all the fine suggestions offered by Limbic~Region, the one I personally like the best is the 6th. That is, port some Perl5 code to Perl6. Try to run it on Pugs. Frequently, you'll run into small bugs that will either be Pugs Bugs, or Perl6 Gotchas. These are both good things to find at this stage in the game. In either case, you would be best to write a test case demonstrating what you discovered. It may sound suspiciously like work, but in my experience, it's a lot of fun! :-)	[reply]
Re^2: Get Involved With Pugs by Limbic~Region (Chancellor) on May 12, 2005 at 12:00 UTC
tphyahoo, You could play a game or you could try and one of the suggestions I listed in the root thread. Cheers - L~R	[reply]
Re^2: Get Involved With Pugs by dragonchild (Archbishop) on May 12, 2005 at 13:45 UTC
You working on Win32 or Cygwin? I haven't been able to get Pugs working for Cygwin yet (due to GHC/Cygwin limitations). If you're not Cygwin, how do you use Pugs? On the Win32 commandline? In general, if you think something isn't in Perl, try it out, because it usually is. :-) "What is the sound of Perl? Is it not the sound of a wall that people have stopped banging their heads against?"	[reply]
Re^3: Get Involved With Pugs by tphyahoo (Vicar) on May 12, 2005 at 15:36 UTC
Win32. All I've done is `pugs -e "{ 'Hello, ', @^x }.('World!').say"` [download] and yep, that was on the win32 commandline.	[reply] [d/l]