Perrin Harkins writes:
Correct Perl style is probably not something that any two people will
ever agree on.
If you use Extreme Programming, the whole team has to agree.
Collective ownership, pair programming, and refactoring all suffer if
you don't have a common coding style. The use of map,
Perrin == Perrin Harkins [EMAIL PROTECTED] writes:
Perrin Someone else will eventually have to maintain them, so I
Perrin write in a way that a novice with a copy of Learning Perl has a hope
Perrin of understanding.
Perrin When I work in an environment that is more Perl-centric, I expand the
On Fri, Nov 01, 2002 at 01:42:45PM -0500, Perrin Harkins wrote:
It sounds like you're saying that you should only use a subset of Perl
as some programmers may not understand the other parts of it?
That is what I'm saying. I'm aware that this is a controversial opinion
in the Perl world.
Tony Bowden wrote:
... but I think that there should be a certain level of ability that
should be assumed when coding commercially ...
My current situation is somewhat unusual because Perl is not the
language that the people I am coding with were hired to write. They are
mostly Java
Franck PORCHER wrote:
But for is a lot easier to read and debug, IMHO Is there a
significant performance difference in using map instead?
My experience is that in most cases, the for construct is used
to apply the same treatment to all the elements of an array,
whence the map
On Fri, Nov 01, 2002 at 03:10:54AM -0500, Perrin Harkins wrote:
There is a time and place for map: when you want to do something
to each element in an array and return the array on the other side.
Otherwise, use for, like this: some_function($_) for array;.
Even when map is not incorrect, I
Tony Bowden wrote:
It sounds like you're saying that you should only use a subset of Perl
as some programmers may not understand the other parts of it?
That is what I'm saying. I'm aware that this is a controversial opinion
in the Perl world. However, I think it's reasonable to know your
Hi
( 02.11.01 13:42 -0500 ) Perrin Harkins:
It's not that map is so evil, but rather that I have often seen people
overuse it (especially after a first-reading of Effective Perl), and
write confusing code with it by jamming too much into the map { some
stuff } @list form.
As a former map
Mike == Mike Miller [EMAIL PROTECTED] writes:
Let's prey that those PHP geeks quickly discover the
true joy of working with functionnals (map and al.).
I have often wondered about the ratio of Perl programmers
still using the C-like for construct. I guess it's rather low.
Mike But for is
On Thu, 31 Oct 2002, Mike Miller wrote:
On Wed, 30 Oct 2002 20:28:11 + (GMT)
Franck PORCHER [EMAIL PROTECTED] wrote:
Let's prey that those PHP geeks quickly discover the
true joy of working with functionnals (map and al.).
I have often wondered about the ratio of Perl programmers
On Thu, 31 Oct 2002, Franck PORCHER wrote:
In fact, regarding the efficiency of the map construct, I often
wondered whether Perl detects map being ran in a void context,
so as to give it an iterative interpretation, avoiding to build
the output list.
IIRC (but I might not) then it does since
Let's prey that those PHP geeks quickly discover the
true joy of working with functionnals (map and al.).
I have often wondered about the ratio of Perl programmers
still using the C-like for construct. I guess it's rather low.
Franck.
On Wed, 30 Oct 2002, Tagore Smith wrote:
Rob Nagler wrote:
12 matches
Mail list logo
