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 speci
On Tue, 12 Nov 2002 17:00:17 +, Dave Whipp wrote:
(cross-posting to perl.qa for other perspectives)
> When I look at this, I find myself wanting to separate the control from the
> data. Here's an alternative:
>
> my @input = qw( 4.5 0.0 13.12343 );
> my @output = qw( 4.5 0.0 13.1234
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 i
On Tue, Nov 12, 2002 at 01:20:04PM -0700, Luke Palmer wrote:
: > =head2 String as vector of ordinals
: >
: > Literals of the form C are parsed as a string
: > composed of characters with the specified ordinals. This
: > is an alternative, more readable way to construct
: > (possibly unicode) stri
> > 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 Tue, Nov 12, 2002 at 03:58:37PM -0800, Michael Lazzaro wrote:
> Or do you build the tree in "flattened" form, and rely on the author to
> get the numbering right?
>
> =section 1 blah
> =section 1.1 subblah
> =section 1.1.1 subsubblah
> =section 1.2 subblah2
> =section 2 blah2
Or number the se
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:2
> 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
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
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
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 wa
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
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,
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), there was s
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
...
=end-section
=section
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 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:03:30PM +0100, Angel Faus wrote:
> This is just a tentative draft, so feel free to delete/add at your own
> taste.
>
> Does it look ok? Any comments? (including grammar errors, of course)
I've tweaked the first bit on literal integers a bit, see what you
think.
=subs
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> From: Angel Faus <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Organization: vLex.com
> Date: Tue, 12 Nov 2002 21:03:30 +0100
> X-SMTPD: qpsmtpd/0.12, http://develooper.com/code/qpsmtpd/
>
> I've written a frist version of the "1.1 -
19 matches
Mail list logo
