On Mar 29, 2007, at 4:20 PM, jerry gay wrote:
On 3/29/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> and i'm not interested in testing every
revision,
> when so many might be coding standards
Why are people even checking things in that fail coding standards?
because not a
On Thursday 29 March 2007 23:03, Joshua Isom wrote:
> One other thing I've noticed is that todo tests sometimes become
> forgotten tests. And since they're sometimes platform specific, they
> don't get fixed for that platform because feature x doesn't have the
> code support. Other than doing a
On Mar 29, 2007, at 10:14 PM, Will Coleda wrote:
On Mar 27, 2007, at 4:45 PM, Allison Randal wrote:
but, we need better smoke tools
So lets document what we need. Right now 'make smoke' generates an
HTML report which is uploaded to the smoke server.
Talk has happened in
On 3/29/07, via RT Will Coleda <[EMAIL PROTECTED]> wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #42170]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42170 >
For steve_p on #parrot.
I find
Good luck w/ your studies. Viable alternatives to SQL are always welcome.
;-)
On 3/23/07, Darren Duncan <[EMAIL PROTECTED]> wrote:
At 7:15 PM -0700 3/23/07, John Beppu wrote:
>You might find Dee interesting:
>
>http://www.quicksort.co.uk/
This Dee project in Python is a worthy thing to study
# New Ticket Created by Will Coleda
# Please include the string: [perl #42170]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42170 >
For steve_p on #parrot.
I find this a little too verbose, but would not object if someon
On Mar 27, 2007, at 4:45 PM, Allison Randal wrote:
but, we need better smoke tools
So lets document what we need. Right now 'make smoke' generates an
HTML report which is uploaded to the smoke server.
Talk has happened in the past about making this more DB like instead
# New Ticket Created by Will Coleda
# Please include the string: [perl #42169]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42169 >
ala recent "IRC discussion..." thread on parrot-porters and put it in
the repository in
Eric Hanchrow wrote:
Here's the relevant bits from my
config file:
[miscellany]
### Set enable-auto-props to 'yes' to enable automatic properties
### for 'svn add' and 'svn import', it defaults to 'no'.
### Automatic properties are defined in the section 'auto-props'.
enable-
Eric Hanchrow wrote:
Here's the relevant bits from my
config file:
[miscellany]
### Set enable-auto-props to 'yes' to enable automatic properties
### for 'svn add' and 'svn import', it defaults to 'no'.
### Automatic properties are defined in the section 'auto-props'.
enable-
On Thu, Mar 29, 2007 at 01:21:27AM -0700, Darren Duncan wrote:
: At 7:28 PM -0700 3/28/07, [EMAIL PROTECTED] wrote:
: > =head1 Multidimensional arrays
: >
: >+Perl 6 arrays are not restricted to being one-dimensional (that's simply
: >+the default). To declare a multidimensional array, you specify
On Thu, Mar 29, 2007 at 04:08:58PM -0700, chromatic wrote:
> On Thursday 29 March 2007 15:44, Steve Peters wrote:
>
> > On Thu, Mar 29, 2007 at 12:51:54PM -0700, Leopold Toetsch via RT wrote:
>
> > Sweeping dirt under the rug doesn't mean that the house has been cleaned
> > up. It means I've tur
Author: larry
Date: Thu Mar 29 16:14:45 2007
New Revision: 14366
Modified:
doc/trunk/design/syn/S09.pod
Log:
clarifications suggested by thom++
Modified: doc/trunk/design/syn/S09.pod
==
--- doc/trunk/design/syn/S09.p
On Thursday 29 March 2007 15:44, Steve Peters wrote:
> On Thu, Mar 29, 2007 at 12:51:54PM -0700, Leopold Toetsch via RT wrote:
> Sweeping dirt under the rug doesn't mean that the house has been cleaned
> up. It means I've turned it into someone else's problem. I'd rather
> Parrot was solid and
Am Freitag, 30. März 2007 00:44 schrieb Steve Peters:
> Sweeping dirt under the rug doesn't mean that the house has been cleaned
> up.
It's not related to hiding other possible errors. Some warnings are just not
appropriate to the usage of the very code, and there are a lot of them.
leo
On Thu, Mar 29, 2007 at 12:51:54PM -0700, Leopold Toetsch via RT wrote:
> Am Mittwoch, 28. März 2007 20:41 schrieb Nicholas Clark:
> > Getting parrot to build under -ansi -pedantic is left as an exercise to the
> > reader.
>
> By filtering other useless and/or nonsensical warnings - yes - else no.
On Wed, Mar 28, 2007 at 07:41:25PM +0100, Nicholas Clark wrote:
> On Tue, Mar 27, 2007 at 05:42:12AM -0700, Steve Peters via RT wrote:
>
> > > Anyway, it's worth noting that although one of functions actually
> > > doesn't
> > > return anything, it is documented as returning a PMC *. So either th
Am Donnerstag, 29. März 2007 23:01 schrieb chromatic:
> On Thursday 29 March 2007 13:27, Leopold Toetsch wrote:
> > > Compactness does not supersede good design.
> >
> > Basically & in theorie yes, but don't always forget performance.
>
> Until we get completeness and correctness and cleanliness, I
> "chromatic" == chromatic <[EMAIL PROTECTED]> writes:
chromatic> The line-ending coding standards tests can be a problem
chromatic> in some cases, where Windows developers add new files
chromatic> with their native format and forget to set the
chromatic> svn:eol-style=native
> > and i'm not interested in testing every revision,
> > when so many might be coding standards
> Why are people even checking things in that fail coding standards?
The line-ending coding standards tests can be a problem in some cases, where
Windows developers add new files with t
On 3/29/07, Nicholas Clark <[EMAIL PROTECTED]> wrote:
> and i'm not interested in testing every revision,
> when so many might be coding standards
Why are people even checking things in that fail coding standards?
because not all coding standard tests are run with 'make test'
On Thursday 29 March 2007 13:27, Leopold Toetsch wrote:
> > Compactness does not supersede good design.
> Basically & in theorie yes, but don't always forget performance.
Until we get completeness and correctness and cleanliness, I really think we
should forget performance. It's awfully diffic
[EMAIL PROTECTED] wrote:
Modified: doc/trunk/design/syn/S09.pod
==
...
-my @calendar[12;*;24]; # "Month" dimension unlimited
+my @calendar[12;*;24]; # day-of-month dimension unlimited/ragged
There's
Am Donnerstag, 29. März 2007 00:00 schrieb Alek Storm:
> On 3/28/07, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> > 1) This ism't needed, these pointers are only valid and needed up to the
> > next
> > sub call/return.
>
> The current_results member already lives in Parrot_Context; this patch
> jus
On Thursday 29 March 2007 13:05, Nicholas Clark wrote:
> I don't think that the stable/development spit in Perl 5 land is broken.
> There is a problem that there aren't enough people with good enough
> knowledge to be committers, and in particular to want to review and apply
> patches supplied by
On Tue, Mar 27, 2007 at 01:45:57PM -0700, Allison Randal wrote:
> It works OK if everyone agrees that one ( or a very
> few) access the maintanence branch
> How many branches are we talking about 1,2 or 10 ?
>Steve_p, I think Nicholas might disagree that
Am Mittwoch, 28. März 2007 20:41 schrieb Nicholas Clark:
> Getting parrot to build under -ansi -pedantic is left as an exercise to the
> reader.
By filtering other useless and/or nonsensical warnings - yes - else no.
leo - been there, done that
Author: larry
Date: Thu Mar 29 12:32:03 2007
New Revision: 14365
Modified:
doc/trunk/design/syn/S04.pod
Log:
missing words spotted by shamu++
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.pod
Author: larry
Date: Thu Mar 29 12:06:16 2007
New Revision: 14364
Modified:
doc/trunk/design/syn/S09.pod
Log:
error spotted by TSa++
Modified: doc/trunk/design/syn/S09.pod
==
--- doc/trunk/design/syn/S09.pod(o
[EMAIL PROTECTED] schreef:
> -Attempting to access an index outside a array's defined range will
> fail:
> +Attempting to access an index outside an array's defined range
> will fail:
Idea for Perl6 test code: detecting (simple) typos in documentation.
--
Affijn, Ruud
"Gewoon is een tijger."
On Thursday 29 March 2007 07:29, Steve Peters via RT wrote:
> Of course, some well defined macros could assist in cleaning this up.
> For example...
>
> #define PARROT_MEM_ALLOCATE(type) \
> (type *)mem_sys_allocate(sizeof(type))
>
> I don't know the Parrot opinion of macros, but it would cer
On 28/03/07, via RT Steve Peters <[EMAIL PROTECTED]> wrote:
# New Ticket Created by Steve Peters
# Please include the string: [perl #42156]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=42156 >
In this next round of cleanu
On Tue Mar 27 10:54:17 2007, doughera wrote:
> On Tue, 27 Mar 2007, Steve Peters wrote:
>
> > # New Ticket Created by Steve Peters
> > # Please include the string: [perl #42151]
> > # in the subject line of all future correspondence about this issue.
> > # http://rt.perl.org/rt3/Ticket/Display
Author: larry
Date: Thu Mar 29 07:11:09 2007
New Revision: 14363
Modified:
doc/trunk/design/syn/S09.pod
Log:
missing blank line supplied by dduncan++
Modified: doc/trunk/design/syn/S09.pod
==
--- doc/trunk/design/syn
Joshua Gatcomb wrote:
On 3/28/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Joshua Gatcomb wrote:
If you could hang out on #parrot (irc.perl.org) when myself, Jonathan,
particle, etc are around - it would go a long way towards getting a
reproduceable test case that can be correctly articulated
Paul Cochrane wrote:
I don't know if it's of much help, but I too am getting the Cygwin
build barfing when miniparrot goes to build
runtime/parrot/include/config.fpmc.
I think that's actually a good sign. Try adding the absolute path to
F and try again. If this is working please see my previ
I don't know if it's of much help, but I too am getting the Cygwin
build barfing when miniparrot goes to build
runtime/parrot/include/config.fpmc.
Paul
HaloO,
[EMAIL PROTECTED] wrote:
+Similarly, within a C<.{}> indexing operation you can use C<*[$idx]>
+to convert from standard indices to user-defined:
+
+@lengths{ *[2] .. Oct } # Same as: @lengths{ Jan .. Oct }
Isn't that same as @length{Mar..Oct}?
--
At 7:28 PM -0700 3/28/07, [EMAIL PROTECTED] wrote:
=head1 Multidimensional arrays
+Perl 6 arrays are not restricted to being one-dimensional (that's simply
+the default). To declare a multidimensional array, you specify it with a
+semicolon-separated list of dimension lengths:
+
+my int @in
39 matches
Mail list logo
