On Saturday 29 April 2006 20:23, Fu, Elva wrote:
> It seems I didn’t express my question very well:-), please let me clarify
> it more detail:
No, I understood you. You have a binary distribution of Perl packaged by
someone besides the official Perl release manager. The package provided by
th
--- "Fu, Elva" wrote:
> It seems there are really an ¡°Integrated¡± test suites existed to test Perl
> itself. Who could give me a hand to find it? Thanks in advance.
I thought chromatic already this question by pointing you at the t/
directories in the Perl source code distribution.
To clarify,
Thank you chromatic & Andrew, I got it now. Thanks again for you kind help!
-Original Message-
From: Andrew Savige [mailto:[EMAIL PROTECTED]
Sent: 2006年4月30日 15:08
To: Fu, Elva; chromatic; perl-qa@perl.org
Subject: RE: Is there an "integrated" test suite/module to test all standard
modul
Ovid wrote:
--- Adam Kennedy <[EMAIL PROTECTED]> wrote:
So I'd like to propose the following for inclusion.
Metric: consistent_newlines
The distribution is awarded a point IF for ALL text files within the
distribution EACH file contains EITHER exclusively unix newlines OR
exclusively Win32 n
On Saturday 29 April 2006 21:50, Damian Conway wrote:
> Is:
>
> > $antler. .bar;
> > $xyzzy. .bar;
> > $blah. .bar;
> > $foo. .bar;
>
> really so intolerable, for those who are gung-ho to line up the method
> names?
I'm still wondering what's awful about:
$antler.bar;
$xyzzy.bar;
Austin Hastings wrote:
> Or, to put it another way: what hard problem is it that you guys are
> actively avoiding, that you've spent a week talking about making
> substantial changes to the language in order to facilitate lining up
> method names?
That's a very good point too.
Initially it's just
* Ovid <[EMAIL PROTECTED]> [2006-04-30 07:20]:
> Sounds like a good idea, but what about strings? You'd need to
> mask those out prior to the test, wouldn't you?
I don’t think so.
Even if the only “funny” newline only appears in a string (and
even it seems to me more likely that this would happe
* Adam Kennedy <[EMAIL PROTECTED]> [2006-04-30 07:00]:
> The Perl::Critic thing could be tricky though.
>
> One of the very few things PPI does that isn't round-trip safe
> (actually, the ONLY thing) is localise the newlines for the
> files it opens.
Why would this have to rely on PPI at all? To
I'm trying play with pugs for the first time. I checked it out from the
repository (r10142) and, after installing ghc 6.4.2, attempted to build
pugs. Fairly quickly, the build dies with the message below. Does anyone
have any hints what the problem might be (I'm not a Haskell person yet,
but I
dear camels,
especially all german speaking camels.
im currently writing a perl6 tutorial in a wiki at:
http://wiki.perl-community.de/bin/view/Wissensbasis/Perl6Tutorial
Please join if you like or help when finished and nothing better there
to translate to english.
Its nearly half ready, vars, op
Op een mooie winterdag (Monday 24 April 2006 00:21),schreef Abe Timmerman:
> Op een mooie winterdag (Sunday 23 April 2006 17:30),schreef Steve Peters:
I am so sorry, I got you mixed up with the other Steve (Hay that is)
Damian Conway skribis 2006-04-30 9:49 (+1000):
> This would make the enormous semantic difference between:
>foo. :bar()
> and:
>foo :bar()
And how is that very different from the enormous semantic difference
between:
foo. .bar()
and:
foo .bar()
that already exists?
chromatic skribis 2006-04-30 2:06 (-0700):
> I'm still wondering what's awful about:
> $antler.bar;
>$xyzzy.bar;
> $blah.bar;
> $foo.bar;
That's what I will do when current long dot stays, but I prefer to keep
things left-aligned to the indentation level. These cascades look messy.
Yuval Kogman skribis 2006-04-30 2:58 (+0300):
> > We need to be careful not to require the language to solve problems that
> > are better solved with tools.
> On that point I agree, but I think it was a question of
> aesthetics... Juerd?
Yes, it was about both aesthetics and the extra wor
Jonathan Lang skribis 2006-04-29 19:08 (-0700):
> Is there a reason that we've been insisting that a long dot should use
> whitespace as filling?
I don't know.
> foo.___.bar
Would still have the problem of clashing with .. when there's no _ in
between.
> foo.___:bar
Would suffice fo
Audrey Tang skribis 2006-04-30 17:31 (+0800):
> Austin Hastings wrote:
> > Or, to put it another way: what hard problem is it that you guys are
> > actively avoiding, that you've spent a week talking about making
> > substantial changes to the language in order to facilitate lining up
> > method na
On 4/30/06 7:44 AM, Juerd wrote:
> Jonathan Lang skribis 2006-04-29 19:08 (-0700):
>> Is there a reason that we've been insisting that a long dot should use
>> whitespace as filling?
>
> I don't know.
>
>> foo.___.bar
>
> Would still have the problem of clashing with .. when there's no _ i
John Siracusa skribis 2006-04-30 8:15 (-0400):
> >> foo.___:bar
> > Would suffice for my needs. Not sure if people are willing to give up
> > their underscore-only method names, though.
> No one's going to use either of these because they're ugly.
"I am not going to use either of these becau
> I don't think it's ugly. It's not any less tidy.
>
> $xyzzy.foo() $xyzzy.foo()
> $fooz.:foo() $fooz.:foo()
> $foo._:foo() $foo. :foo()
> $da.__:foo() $fa. :foo()
>
> My variable names aren't so long that I'm likely to have
> foo.___:bar, and $foo.__:bar is clean.
B
Juerd wrote:
> foo.___:bar
Would suffice for my needs. Not sure if people are willing to give up
their underscore-only method names, though.
When is the last time that you saw an underscore-only method name?
Gaal Yahas wrote:
But it doesn't work across lines:
Take another look at my o
# New Ticket Created by jerry gay
# Please include the string: [perl #39035]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39035 >
dynpmc build fails during perlarray on win32 with msvc, revision 12465:
D:\usr\lo
On Sat, Apr 29, 2006 at 05:15:08PM +0200, Juerd wrote:
: Larry indicated that changing the long dot would have to involve
: changing the first character. The only feasible solution in the "tiny
: glyphs" section was the backtick. I refrain from explaining why that
: will widely be considered a bad
Gaal Yahas skribis 2006-04-30 16:05 (+0300):
> But it doesn't work across lines:
> $and_a_long_one_I_still_want_to_align.
> :foo()
Explain to me why it wouldn't work, please. I don't get it.
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_h
Larry Wall skribis 2006-04-30 9:58 (-0700):
> On Sat, Apr 29, 2006 at 05:15:08PM +0200, Juerd wrote:
> : Larry indicated that changing the long dot would have to involve
> : changing the first character. The only feasible solution in the "tiny
> : glyphs" section was the backtick. I refrain from e
On Sun, Apr 30, 2006 at 09:58:21AM -0700, Larry Wall wrote:
> Neither of those are currently legal in infix position. The backslash
> Backslash also has the advantage of making sense to a C programmer:
>
> $foo\
> .foo();
So this also would be legal?
$foo
On Sun, Apr 30, 2006 at 07:01:06PM +0200, Juerd wrote:
> Gaal Yahas skribis 2006-04-30 16:05 (+0300):
> > But it doesn't work across lines:
> > $and_a_long_one_I_still_want_to_align.
> > :foo()
>
> Explain to me why it wouldn't work, please. I don't get it.
This form certainly w
Author: larry
Date: Sun Apr 30 10:43:33 2006
New Revision: 9042
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S04.pod
doc/trunk/design/syn/S12.pod
Log:
Long dot is now introduced by backslash.
Modified: doc/trunk/design/syn/S02.pod
On Sun, Apr 30, 2006 at 06:33:01PM +0100, Nicholas Clark wrote:
: On Sun, Apr 30, 2006 at 09:58:21AM -0700, Larry Wall wrote:
:
: > Neither of those are currently legal in infix position. The backslash
:
: > Backslash also has the advantage of making sense to a C programmer:
: >
: > $foo\
:
On Sun, Apr 30, 2006 at 03:47:54AM +0300, Yuval Kogman wrote:
> On Sat, Apr 29, 2006 at 18:12:34 +0100, Nicholas Clark wrote:
> > On Sat, Apr 29, 2006 at 05:59:37PM +0200, Juerd wrote:
> > > I get a message like this for every message that I send to this list.
> > > Trying to contact [EMAIL PROTECT
In a message dated Sun, 30 Apr 2006, [EMAIL PROTECTED] writes:
The whitespace in the middle may include any of the comment forms above.
-Because comments always count as whitespace, the dots in
+Because comments always count as whitespace, the C<\.> in
-$object.#{ foo }.say
+$object\#{ f
bernhard++ # this seems to have been fixed
On 4/30/06, via RT jerry gay <[EMAIL PROTECTED]> wrote:
# New Ticket Created by jerry gay
# Please include the string: [perl #39035]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=
# New Ticket Created by jerry gay
# Please include the string: [perl #39038]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39038 >
#39035 has been fixed, so dynpmc's compile again. but they won't link
due to an unresolved
Larry Wall wrote:
Seems so to me too. I don't see much downside to \. as a long dot.
The only remaining problem that I see for the long dot is largely
orthogonal to the selection of the first and last characters - namely,
that your only choice for filler is whitespace. Although the C<\.>
opti
Author: larry
Date: Sun Apr 30 18:51:14 2006
New Revision: 9047
Modified:
doc/trunk/design/syn/S02.pod
Log:
More long dot cleanup from trey++ et al.
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/
Author: larry
Date: Sun Apr 30 18:55:42 2006
New Revision: 9048
Modified:
doc/trunk/design/syn/S02.pod
Log:
Couple more long dots.
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod(or
35 matches
Mail list logo
