Re: reporting bugs
Richard Hainsworth wrote: > s/has appeared/has NOT appeared/ > > Richard Hainsworth wrote: >> I posted an email to per6-all asking about how one should go about >> reporting bugs. That message has appeared on the list. >> That's because perl6-all is a meta list, which subscribes you to p6l, p6c and p6u. You still have to send your email to one specific list (for example perl6-compiler would have been the appropriate one). Cheers, Moritz
Re: reporting bugs
Patrick R. Michaud wrote: On Sun, Jan 04, 2009 at 05:20:56PM +0300, Richard Hainsworth wrote: I posted an email to per6-all asking about how one should go about reporting bugs. That message has appeared on the list. So again: how can bugs be reported? See the "Reporting bugs" section of README file in languages/perl6. (Honestly, I don't know why we call such files "README", since nobody ever does. I think I'll rename the file to "IGNOREME" -- maybe it'll get some attention then. :-) Perhaps modify the Makefile: # targets for building a standalone perl6. # (We're not quite ready to make this a default target.) perl6$(EXE): perl6.pbc $(PBC_TO_EXE) perl6.pbc @echo "$@ built: for more info, or to file bugs, see the README"
Re: reporting bugs
On Sun, 4 Jan 2009, Patrick R. Michaud wrote: On Sun, Jan 04, 2009 at 05:20:56PM +0300, Richard Hainsworth wrote: I posted an email to per6-all asking about how one should go about reporting bugs. That message has appeared on the list. So again: how can bugs be reported? See the "Reporting bugs" section of README file in languages/perl6. (Honestly, I don't know why we call such files "README", since nobody ever does. I think I'll rename the file to "IGNOREME" -- maybe it'll get some attention then. :-) Call it "WHEN-PERL-6-WILL-BE-DONE" -- then it will get attention :). - | Name: Tim Nelson | Because the Creator is,| | E-mail: wayl...@wayland.id.au| I am | - BEGIN GEEK CODE BLOCK Version 3.12 GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V- PE(+) Y+>++ PGP->+++ R(+) !tv b++ DI D G+ e++> h! y- -END GEEK CODE BLOCK-
Re: reporting bugs
On Sun, Jan 04, 2009 at 05:20:56PM +0300, Richard Hainsworth wrote:
> I posted an email to per6-all asking about how one should go about
> reporting bugs. That message has appeared on the list.
>
> So again: how can bugs be reported?
See the "Reporting bugs" section of README file in languages/perl6.
(Honestly, I don't know why we call such files "README", since nobody
ever does. I think I'll rename the file to "IGNOREME" -- maybe it'll
get some attention then. :-)
> Eventually, I found reference to perlbug and opened an account. But I
> cant find a way to submit a bug.
>
> Some requests:
> a) When I strike a bug, perl6 (rakudo) dumps alot. Could this behaviour
> be modified with a verbose option on the perl6 command line?
I'm working on this. Parrot doesn't give us a lot of control over
backtrace behavior at the moment -- it's either all-or-nothing.
I might implement a switch somewhere.
> b) Also, what needs to be stated? I used svn to download the latest
> parrot. So, I should be stating the latest revision number. "perl6 -v"
> doesnt provide this.
We haven't come up with a good way to fetch the latest revision number
for use with a -v option to perl6. If you know of one (and that will
work even if someone obtains Rakudo via tarball or git or a non-svn
mechanism), we can certainly add it.
> I was going to describe the bugs, but I just checked the test results in
> S05 and found the things I cant get working are not yet implemented.
>
> There isnt any table of these anywhere. Could we get one?
http://www.perlfoundation.org/perl6/index.cgi?rakudo%20feature%20status
Feel free to modify this list.
>
> Patrick! Do you want feed back about things that cant be done, but
> should be done?
>
> If so, I would like to have m:i/ / and m/ a {say 'yes'} /
m:i/ ... / can currently be done with /:i ... / .
Getting closures to work inside of regexes is a bit tricky at the
moment, because it implies that PGE (our regex engine) has to
know how to call the Perl 6 parser and do the right thing with
whatever it gets back. That's coming in the not-too-distant
future, but it's by no means "trivial" to implement.
Pm
Re: reporting bugs
On 2009 Jan 4, at 9:20, Richard Hainsworth wrote: I posted an email to per6-all asking about how one should go about reporting bugs. That message has appeared on the list. So again: how can bugs be reported? A quick google of "rakudo bug" points to rakudo...@perl.org -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu electrical and computer engineering, carnegie mellon universityKF8NH
Re: reporting bugs
s/has appeared/has NOT appeared/ Richard Hainsworth wrote: I posted an email to per6-all asking about how one should go about reporting bugs. That message has appeared on the list.
