[perl #115158] a2p wrongly considers string literal "0" is always false

On Wed Aug 28 08:04:05 2013, zefram@fysh.org wrote:
> Ralph Corderoy wrote:
> >                                              If the string is a
> >constant in the source then it's true, not false.  Perl's a2p(1) doesn't
> >handle this subtlety.
> 
> a2p isn't meant to be an implementation of awk, but an approximate
> translator.  It deliberately compromises on awk semantics in order
> to produce idiomatic Perl.  So this problem, arising from a low-level
> difference in language semantics, is unfortunate but not a bug.

Do you think I should close this as being not-a-bug, or leave it open as
a wishlist item?  (Is it a wishlist item, or a ‘won’t fix’?)

-- 

Father Chrysostomos


---
via perlbug:  queue: perl5 status: open
https://rt.perl.org:443/rt3/Ticket/Display.html?id=115158

• [perl #115158] a2p wrongly considers string literal "0" is always false by Ralph Corderoy
• Re: [perl #115158] a2p wrongly considers string literal "0" isalways false by Zefram
• Re: [perl #115158] a2p wrongly considers string literal "0" is always false by Ralph Corderoy
• [perl #115158] a2p wrongly considers string literal "0" is always false by Father Chrysostomos via RT
• Re: [perl #115158] a2p wrongly considers string literal "0" isalways false by Zefram
• a2p/s2p by Johan Vromans
• Re: a2p/s2p by James E Keenan
• Re: a2p/s2p by Nicholas Clark
• Re: a2p/s2p by ilmari