AT == Audrey Tang [EMAIL PROTECTED] writes:
AT Uri Guttman wrote:
one of these days when i have tuits of large circumference, i will do a
nit pass over as much of the A/E/S as i can handle before my brain
explodes. having done tech editing for perl books is good training for
this.
Given perl6's use of unicode as a basis, could we get curly quotes,
both single and double, to do the same things that straight quotes do?
That is: text does the same thing as text, and 'text' does the
same thing as 'text'. Other than looks neat, why do this? Because
curly-quotes come in
Uri Guttman wrote:
one of these days when i have tuits of large circumference, i will do a
nit pass over as much of the A/E/S as i can handle before my brain
explodes. having done tech editing for perl books is good training for
this. in fact it would be a good idea to have several such passes
demerphq wrote:
On 4/2/06, Adam Kennedy [EMAIL PROTECTED] wrote:
demerphq wrote:
On 4/1/06, Adam Kennedy [EMAIL PROTECTED] wrote:
Similarly
if somebody has an error in their Build.PL or Makefile.PL are you
going to say that the installer doesnt work?
Yes, absolutely.
So you would file a
Please no svn checkins until further notice.
leo
On behalf of the Parrot team I'm proud to announce another
monthly release of Parrot.
I'd like to thank all involved people as well as our
sponsors for supporting us.
What is Parrot?
Parrot is a virtual machine aimed at running Perl6 and other dynamic
languages, see http://www.parrotcode.org/
Larry Wall schreef:
Ruud H.G. van Tol:
Uri Guttman:
When cast into an array, you can access all the positional
arguments; Into a hash, all named arguments; Into a scalar, the
invocant; Into code, into slurpy nameless block.
The last 'into' should be 'the'.
And it has become 'its', which
Uri Guttman schreef:
you might as well attribute the s:g/Into/into/ to dr. ruud.
Right, s:g/I/i/ is all that remained. I really was amazed by your new
capitalization style.
:)
--
Affijn, Ruud
Gewoon is een tijger.
(posted via news://nntp.perl.org again)
Adam Kennedy wrote:
While the code for the distribution might be able to die like this,
the INSTALLER should fail in a way that is detectable and automatable.
If the Cused warnings.pm module can't be found, it crashes
(specifically, dies) and say it can't find warnings. But the problem
I have done the two programmers, one terminal approach advocated by
Beck for XP developments (not just TDD) and it worked well. We delivered
on time with all features present and correct (where correct means the
application passed the customers Business Acceptance Tests - first
time).
I should
I've been spending a lot of time the past 6 months (more?) doing source
code cleanup on the Perl 5 source code.
I'd like to spend some time doing the same for Parrot, too. I hope that
doing the kind of maintenance I'm interested in makes things easier for
the core Parrot developers do their
On Sat, Apr 01, 2006 at 04:04:42PM -0800, Jeffrey Thalhammer wrote:
I have never actually had an opportunity to practice
this, but I've always felt that the most obvious way
to combine test-driven development with pair
programming was to have one person write test code
while the other person
12 matches
Mail list logo
