Re: [PATCH RFC 0/5] Patches to avoid reporting conversion changes.

4 messages, 3 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH RFC 0/5] Patches to avoid reporting conversion changes.

From: Randal L. Schwartz <hidden>
Date: 2016-06-15 22:48:40

quoted
quoted
quoted
quoted
"Jari" == Jari Aalto [off-list ref] writes:
quoted
Right, but without looking, is it $OS_ERROR or $OSERROR?
Jari> I don't see any difference, because that variable is always within the
Jari> close context of previous statements. The reader would consult the lines
Jari> above.

Yes, once it's already *in* the program.  But I bet you had to *look
them up* to add them.

And if you weren't familiar with Perl, you'd still have to *look them
up* to get the punctuation variables.

You're just trading one problem for another.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
[off-list ref] <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion

Re: [PATCH RFC 0/5] Patches to avoid reporting conversion changes.

From: Sverre Rabbelier <hidden>
Date: 2016-06-15 22:48:40

Heya,

On Sat, Apr 17, 2010 at 21:34, Randal L. Schwartz [off-list ref] wrote:
Yes, once it's already *in* the program.  But I bet you had to *look
them up* to add them.
Yes, but once they're there nobody has to look them up. It's moving
the problem from having to look up what it means on _and_ write, to
just write.

-- 
Cheers,

Sverre Rabbelier

Re: [PATCH RFC 0/5] Patches to avoid reporting conversion changes.

From: Jakub Narebski <hidden>
Date: 2016-06-15 22:48:40

Sverre Rabbelier [off-list ref] writes:
On Sat, Apr 17, 2010 at 21:34, Randal L. Schwartz [off-list ref] wrote:
quoted
Yes, once it's already *in* the program.  But I bet you had to *look
them up* to add them.
Yes, but once they're there nobody has to look them up. It's moving
the problem from having to look up what it means on _and_ write, to
just write.
We use idiomatic C, e.g.

  if (!strcmp(option, "warn")) {

not

  if (strcmp(option, "warn") == 0) {


We use idiomatic Perl, e.g.

  %hash = map { $_ => 1 } @list;

not

  use English qw(-no_match_vars);

  %hash = map { $ARG => 1 } @list;

-- 
Jakub Narebski
Poland
ShadeHawk on #git

Re: [PATCH RFC 0/5] Patches to avoid reporting conversion changes.

From: Sverre Rabbelier <hidden>
Date: 2016-06-15 22:48:40

Heya,

On Sun, Apr 18, 2010 at 00:32, Jakub Narebski [off-list ref] wrote:
We use idiomatic C, e.g.
Agreed.
We use idiomatic Perl, e.g.
Ah, I thought that the discussion was about whether the "$_" syntax
was idiomatic or not. It got the impression that the "$ARG etc. is a
failed experiment" was Randal's personal opinion, but if that's how
the perl community has decided that things should be done than that's
of course how we should do it :).

-- 
Cheers,

Sverre Rabbelier
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help