Greg McCarroll [EMAIL PROTECTED] writes:
* Piers Cawley ([EMAIL PROTECTED]) wrote:
David Cantrell [EMAIL PROTECTED] writes:
On Tue, Jan 09, 2001 at 11:25:18AM +, Greg McCarroll wrote:
6.) regular expressions are not the only way to code, length and
substr
* Piers Cawley ([EMAIL PROTECTED]) wrote:
Greg McCarroll [EMAIL PROTECTED] writes:
* Piers Cawley ([EMAIL PROTECTED]) wrote:
David Cantrell [EMAIL PROTECTED] writes:
On Tue, Jan 09, 2001 at 11:25:18AM +, Greg McCarroll wrote:
6.) regular expressions are not the only
Greg McCarroll sent the following bits through the ether:
in my original rule it was all to do with good programming style, not
eeking out every bit of performance, my reply was actually that i
thought dave choose a very grey area in terms of programming style
Indeed. And someone mentioned
How does the output compare to XML::Simple::XMLout() ?
I found XML::Simple::XMLout() to be deeply yucky, as it kind of randomly
chooses to go for sub elements or attributes based on phases of the moon*.
Also, it will happily output invalid XML if you have invalid data in your
datastructure.
Leon Brocard [EMAIL PROTECTED] writes:
Greg McCarroll sent the following bits through the ether:
in my original rule it was all to do with good programming style, not
eeking out every bit of performance, my reply was actually that i
thought dave choose a very grey area in terms of
Nathan Torkington [EMAIL PROTECTED] writes:
David Cantrell writes:
From what I can tell, there ain't a lot happening.
As Piers said, we are blocked on Larry. We're working on some
interpreter design now, but some language issues really need to be
nailed down before we know what we're
Piers Cawley sent the following bits through the ether:
This time. The discussion has been back and forth on various lists,
usually with benchmarks.
Thou shalt optimise for programmer time unless absolutely necessary,
when thou shalt Benchmark and quoth both the benchmark and the
results.
On Jan 9, 8:24am, Nathan Torkington wrote:
As Piers said, we are blocked on Larry. We're working on some
interpreter design now, but some language issues really need to be
nailed down before we know what we're going to be writing.
Are there any plans to keep the RFC process going in the
Anyone got Richard Clamp's mobile no? He's due here now...
--
Dave Hodgkinson, http://www.hodgkinson.org
Editor-in-chief, The Highway Star http://www.deep-purple.com
Apache, mod_perl, MySQL, Sybase hired gun for, well, hire
Piers Cawley writes:
As Piers said, we are blocked on Larry. We're working on some
interpreter design now, but some language issues really need to be
nailed down before we know what we're going to be writing.
Any idea how long we're going to stay blocked?
None whatsoever. Many phone
David Hodgkinson wrote:
Anyone got Richard Clamp's mobile no? He's due here now...
07720 298487
I think
David Hodgkinson [EMAIL PROTECTED] writes:
Simon Wistow [EMAIL PROTECTED] writes:
I think
Ta,
How did he do then?
:-
--
1024/D9C69DF9 steve mynott [EMAIL PROTECTED]
microsoft: where do you want to go today?
linux: where do you want to go tomorrow?
bsd: are you guys coming or what?
* Nathan Torkington ([EMAIL PROTECTED]) wrote:
We're going to use RFCs for future additions to Perl, we just need to
find some good filters that will prevent them from consuming
everyone's time.
how about adding a field on the RFC template such as, ``forum initially
discussed in'' - then
13 matches
Mail list logo
