On Tue, Nov 12, 2002 at 09:03:30PM +0100, Angel Faus wrote:
> Does it look ok?
Sure.
> Any comments? (including grammar errors, of course)
Here are mine.
> -------------------------------------------
> =subsection Literal Values
>
> =head1 Literal numbers
>
> =head2 Integers
>
> Integers can be represented by its decimal representation,
> such as:
Integers can be expressed by decimal notation, for instance:
>
> my $x = 14; # stores the integer 14 in $x
>
I don't know if it would help or hinder, but I think there should be a
sentence like:
Decimal notation is the same positional notation we all learned
in grade school with the ones position at the far right, then
immediately to the left of that is the tens position, then
hundreds, and so forth
> For example, the integer 30 can be written in hexadecimal
> base in two equivalent ways:
>
> my $x = 16:1D
> my $x = 16:1.14
>
> This two representations are incompatible, so writing
> something like C<16:D.13> will generate a compile-time error.
Also note that a compile-time error will be generated if you
specify a "digit" that is larger than your radix can support.
For instance,
my $x = 3:23; # error
Is there some more generic term for number-in-some-arbitrary-radix?
"Digit" always means base-10 numbers to me. (I'll coin "radit" if I
have to ;-)
What happens with this one:
256:255.255..0 # same as 256:255.255.0.0 ?
# or error?
> Finally, you can create negative integers prepending the
> C<-> character.
>
> For example:
>
> my $x = 18;
> my $x = -18;
my $x = -256:245.234;
my $x = -2:101001;
I wonder if all of the "my $x =" parts should just be removed. The
reader doesn't need to know about assignment, variables or scope
declarators to learn about literals.
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
