> *Allowing* typing is not the same as *demanding* typing. Adding types will
> not make the 'universal scalar variable' any less accessible or convenient.
My mistake, I believed that the aforementioned types would become a
requirement ala C/C++ and many other languages.
Greg
-
Gregory S Hayes wrote:
>
> Types just seem so very un-perl. There is much to be said for the
> universal scalar vairable. I'm not sure I fully understand just why we
> NEED types in the language.
> So what are the benifits of types?
Note: I am *not* claiming to be pro-types.
However, in cases
Gregory S Hayes wrote:
> Types just seem so very un-perl. There is much to be said for the
> universal scalar vairable. I'm not sure I fully understand just why we
> NEED types in the language. We have functions such as:
>
> my $integervalue = int($value);
>
> and...
>
> my $float = sprintf("%2.2f
Nathan Wiger wrote:
>
> > Programs will specify arithmetic processing in typical Perl fashion:
> >
> > use integer qw(32bit unsigned);
> > use integer qw(64bit);
> >
> > Perl semantics will reflect this value until the end of current block.
>
> I wonder if this wouldn't be better handled on
> Programs will specify arithmetic processing in typical Perl fashion:
>
> use integer qw(32bit unsigned);
> use integer qw(64bit);
>
> Perl semantics will reflect this value until the end of current block.
I wonder if this wouldn't be better handled on an item-by-item basis
like other lang
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Fuller integer support in Perl.
=head1 VERSION
Maintainer: Shane Kerr <[EMAIL PROTECTED]>
Date: 11 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 209
Version: 1
Status: Developing
=head1 ABS
