Re: Managing breakages across Rakudo versions

2012-07-10 Thread Nicholas Clark
On Thu, Jul 05, 2012 at 02:39:00PM +0200, Moritz Lenz wrote: > Am 05.07.2012 07:11, schrieb Patrick R. Michaud: > > 3. Str.bytes > > > > The C<.bytes> method on C has always been somewhat problematic; in > > Perl 6 > > we typically think of strings in terms of characters, codepoints, graphemes,

Re: Managing breakages across Rakudo versions

2012-07-06 Thread Patrick R. Michaud
On Thu, Jul 05, 2012 at 02:39:00PM +0200, Moritz Lenz wrote: > Am 05.07.2012 07:11, schrieb Patrick R. Michaud: > >1. ? quantifier in regexes > > > >The C quantifier used to be specified to capture matches > >in the same manner as C<*> and C<+> -- that is, it produced > >a List of Match objects in

Re: Managing breakages across Rakudo versions

2012-07-05 Thread yary
On Thu, Jul 5, 2012 at 8:39 AM, Moritz Lenz wrote: >> Ultimately the Perl 6 specification says that version numbers are >> supposed to be able to manage these sorts of issues for us; i.e., if >> a program says  C, then it gets all of the semantics of >> exactly version 6.0.2, regardless of any dep

Re: Managing breakages across Rakudo versions

2012-07-05 Thread Moritz Lenz
Am 05.07.2012 07:11, schrieb Patrick R. Michaud: The first category of breakages are places where the Perl 6 specification has changed from what Rakudo currently implements. 1. ? quantifier in regexes The C quantifier used to be specified to capture matches in the same manner as C<*> and C<+>

Managing breakages across Rakudo versions

2012-07-04 Thread Patrick R. Michaud
Switching over to the 'nom' branch of Rakudo introduced a large number of regressions and changes that affected many users of Rakudo. I know all of the core developers agree that this was really not a good thing, and we want to work very hard to avoid such instabilities in the future. Ideally a