Follow-up Comment #26, bug #67612 (group groff):

Thanks.  I think no longer changing the 1 to a 2 at the call site makes the
comment unnecessary, but I won't object to too much code commenting.

[comment #24 comment #24:]
> Perl, like C before it and C++ alongside it, has shown a
> stubborn reluctance to embrace an explicit Boolean type.

The parallel isn't really valid: unlike C and C++ variables, Perl variables
are untyped, so the concept of a boolean variable is meaningless in Perl.
It'd be weird to introduce a typing system where a variable is either boolean
or nonboolean; if you introduce types into Perl variables, you'd want to cover
all types, and then you're looking at a language redesign that makes it not
really Perl anymore.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?67612>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to