Jonathan Scott Duff wrote:
Or number the sections like this:
=section # blah
=section ## subblah
=section ### subsubblah
=section ## subblah2
=section # blah2
And let the author only worry about sectioning and not about
numbering at all.
I like that decently. Obviously, making authors
I've written a frist version of the 1.1 - Literal Values subsection
(in Michael's schema).
It discusses the different ways of creating literal numbers and
strings in perl6.
There are no tests, and the format may be outdated. I will gladly
resubmit this in a more complete form.
I have
Literal Values
=head1 Literal numbers
=head2 Integers
Integers can be represented by its decimal representation,
such as:
s/Integers/An integer/
my $x = 14; # stores the integer 14 in $x
See the Lquotes section for a full explanation
of the interpolation mechanism and a list
.
=subsection Literal Values
=head1 Literal numbers
=head2 Integers
There are many ways to specify literal numeric values in perl, but they
default to base 10 for input and output. Once the number has been read
by perl it becomes just a magnitude. That is it loses all trace of the
way it was originally
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
On Tue, Nov 12, 2002 at 09:11:24PM +, Andrew Wilson wrote:
For example:
my $i = 2:101110; # binary
my $j = 3:1210112; # tertiary
my $k = 8:1270; # octal
Printing these would give 46, 1310, and 696 respectively.
Hmm. As companion to specifying
On Tuesday, November 12, 2002, at 12:03 PM, Angel Faus wrote:
=subsection Literal Values
=head1 Literal numbers
=head2 Integers
Rather than using =head, each should be a subsection.
What should be the syntax for closing a section?
=section title
...
=end-section
Angel Faus wrote:
I've written a frist version of the 1.1 - Literal Values subsection
(in Michael's schema).
Alright, I have the tests done to match this section of the documentation.
Well, everything except 'bit', since the last time I checked (and this
could be resolved by now
Michael Lazzaro:
# What should be the syntax for closing a section?
How about the empty string? Isn't the end of a section defined by EOF
or when the next section starts?
--Brent Dax [EMAIL PROTECTED]
@roles=map {Parrot $_} qw(embedding regexen Configure)
Wire telegraph is a kind of a very,
On Tuesday, November 12, 2002, at 04:08 PM, Brent Dax wrote:
Michael Lazzaro:
# What should be the syntax for closing a section?
How about the empty string? Isn't the end of a section defined by EOF
or when the next section starts?
I mean if you can have sections inside sections, how do you
On Tue, 12 Nov 2002 17:56:28 +, Joseph F. Ryan wrote:
Alright, I have the tests done to match this section of the documentation.
Well, everything except 'bit', since the last time I checked (and this
could be resolved by now), there was some debate over Boolean types, and
I know bit was
chromatic wrote:
On Tue, 12 Nov 2002 17:56:28 +, Joseph F. Ryan wrote:
For the most part, they look fine to me. I'm a little concerned about some of
the numeric tests:
output_is('CODE', 'OUT', Simple Floats);
print 4.5;
print 0.0;
print 13.12343
CODE
4.50.013.12343
OUT
I'd be more
Michael Lazzaro:
# On Tuesday, November 12, 2002, at 04:08 PM, Brent Dax wrote:
# Michael Lazzaro:
# # What should be the syntax for closing a section?
#
# How about the empty string? Isn't the end of a section
# defined by EOF
# or when the next section starts?
#
# I mean if you can
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Date: Tue, 12 Nov 2002 15:22:53 -0600
From: Jonathan Scott Duff [EMAIL PROTECTED]
What happens with this one:
256:255.255..0 # same as 256:255.255.0.0 ?
# or error?
On the contrary, it's
On Tue, Nov 12, 2002 at 05:38:00PM -0700, Luke Palmer wrote:
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Date: Tue, 12 Nov 2002 15:22:53 -0600
From: Jonathan Scott Duff [EMAIL PROTECTED]
What happens with this one:
256:255.255..0 # same as 256:255.255.0.0 ?
output_is('CODE', 'OUT', Simple Floats);
print 4.5;
print 0.0;
print 13.12343
CODE
4.50.013.12343
OUT
I'd be more comfortable with a newline between the numbers, just in case.
It's
not an issue in the string tests.
Alright, fine by me; I was wondering on that myself. Done
On Tue, Nov 12, 2002 at 01:20:04PM -0700, Luke Palmer wrote:
: =head2 String as vector of ordinals
:
: Literals of the form Cv1.2.3.4 are parsed as a string
: composed of characters with the specified ordinals. This
: is an alternative, more readable way to construct
: (possibly unicode)
On Tue, 12 Nov 2002, Michael Lazzaro wrote:
What should be the syntax for closing a section?
I'm partial to the LaTeX approach, where you specify the level and the
computer figures out the rest. It seems like either level or closing-tag
is sufficient by itself. Levels put all the information
18 matches
Mail list logo
