Damian --
Good. I don't remember where I first heard about doing it that way
vs. from the left, but the results going from the right to left
are typically better looking than from left to right, and I use that
way exclusively now.
Regards,
-- Gregor
On Sat, 2004-02-28 at 15:54, Damian Conway w
Damian Conway wrote:
Mark A. Biggar wrote:
Expect wouldn't that produce a extra blank line if $text is short?
Nope. Formats only generate text lines if at least one of their fields
interpolates at least one character.
Damian
What if I want to interpolate an empty string and let the fill
char
Mark A. Biggar wrote:
Expect wouldn't that produce a extra blank line if $text is short?
Nope. Formats only generate text lines if at least one of their fields
interpolates at least one character.
Damian
Simon Cozens wrote:
It may take a *couple* of nights, but the elves will be at work.
Bless their pointy little hats/ears/beards/shoes! ;-)
Damian
Luke Palmer wrote:
Arn't there cases where the overflow field want to be bigger then the
first field? Something the ends up looking like:
LABEL: texttexttextexttexttext
texttextexttextetexttexttextte
xttexttexttexttexttexttextttex
where LABEL is in one field and text... is in an oveflow block?
Luke Palmer wrote:
Mark A. Biggar writes:
Larry Wall wrote:
On Sat, Feb 28, 2004 at 11:59:15AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: So, what I'm looking for is more explicit phrasing around "immediately
: above". In the example, the column range for the overflow field is
: exactly th
Mark A. Biggar writes:
> Larry Wall wrote:
>
> >On Sat, Feb 28, 2004 at 11:59:15AM -0800, Gregor N. Purdy wrote:
> >: Smylers --
> >:
> >: So, what I'm looking for is more explicit phrasing around "immediately
> >: above". In the example, the column range for the overflow field is
> >: exactly th
Gregor N. Purdy wrote:
In the section "He doth fill fields..." we see an example of Fill
Justification where two spaces fit between every word. This doesn't
give us an idea of how spaces are distributed if the number of
spaces needed does not divide evenly into the number of interstices.
Currently
Smylers wrote:
The :fill option gets a brief mention on page 10, but I didn't spot it
anywhere else or being used in an example:
There is also a general C<:fill> option that sets the default sequence
for any filling that isn't otherwise specified.
That suggests there's a hierarchy of options
Larry Wall wrote:
On Sat, Feb 28, 2004 at 11:59:15AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: So, what I'm looking for is more explicit phrasing around "immediately
: above". In the example, the column range for the overflow field is
: exactly the same as that of the $method field in the pr
[EMAIL PROTECTED] (Damian Conway) writes:
> Thanks for those. We'll leave them out overnight and see if the elves
> will make them disappear from the various on-line versions. ;-)
It may take a *couple* of nights, but the elves will be at work.
--
Gods, you know your house is full of goths when
Smylers wrote:
Praise to Damian for Exegesis 7: the new formats sound very
well-thought-out, flexible, easy-to-use, and extensive -- as well as
being implemented and available right now. I've never used formats in
Perl 5, but I could see myself using Perl6::Form.
Thank-you.
I have a few questio
Gregor N. Purdy wrote:
The Exegesis mentions the Perl6::Slurp module, but I don't see it
on CPAN. Is it just a race condition?
Race condition. That is, I'm racing to get it out. That process is being
slowed by the fact that I'm still designing parts of the interface in line
with feedback from Lar
Gregor N. Purdy wrote:
So, what I'm looking for is more explicit phrasing around "immediately
above". In the example, the column range for the overflow field is
exactly the same as that of the $method field in the prior "picture".
But, what does it do if it doesn't match *exactly*? Is it an error,
Gregor N. Purdy wrote:
In "From the crown of his head to the sole of his foot..." (clearly
a reference to a Gilligan's Island episode where Lovey said something
similar :), we have:
:header{ ..., odd => "Act, $act, Scene $scene...", ... }
and below, text indicating that it will
"prepend
Smylers wrote:
I take "valid identifier" to mean something which is syntactically valid
as an identifier, rather than something that is in the finite set of
identifiers which C actually uses.
Correct.
Although, as Larry pointed out, given the compile-time nature of option keys,
there's no reason
Smylers wrote:
The C<:page{:length}> sub-option (page 12) is described in the text as
having a default value of infinity but in a comment in the example above
of being 60. How so?
Is that the text normally isn't split into pages at all (so effectively
giving a single page of infinite length), but
Gregor N. Purdy wrote:
Smylers already pointed out a few errors in the document, but
here are a few others I noticed:
* In "Why, how now, ho! From whence ariseth this?"
We have this near the top:
type FormArgs ::= Str|Array|Pair;
and this below:
type FormArgs ::
On Sat, Feb 28, 2004 at 12:32:37PM -0800, Larry Wall wrote:
: Now I'm supposing that & binds tighter than | as usual, so the
: brackets wouldn't always be necessary:
:
: & +
: |
: & +
Although, of course, that should probably be written:
& [ + | + ]
or really, just
& <
On Sat, Feb 28, 2004 at 11:56:52AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: I think the claim in E7 is stronger, that not only does the string match
: the identifier pattern, but that it is a 'valid' (known, declared)
: identifier. Else, what would be the point of saying both:
:
: * "cont
On Sat, Feb 28, 2004 at 11:59:15AM -0800, Gregor N. Purdy wrote:
: Smylers --
:
: So, what I'm looking for is more explicit phrasing around "immediately
: above". In the example, the column range for the overflow field is
: exactly the same as that of the $method field in the prior "picture".
: Bu
On Sat, Feb 28, 2004 at 02:42:47AM -0500, Austin Hastings wrote:
: Another hypothetical:
:
: Suppose you have a browser (which understands "language" traits)
: or a word processor (which stores "style" and/or "font" information)
: that is storing some not-text-only string-like things via scalar
:
Smylers --
So, what I'm looking for is more explicit phrasing around "immediately
above". In the example, the column range for the overflow field is
exactly the same as that of the $method field in the prior "picture".
But, what does it do if it doesn't match *exactly*? Is it an error,
does it hav
Smylers --
I think the claim in E7 is stronger, that not only does the string match
the identifier pattern, but that it is a 'valid' (known, declared)
identifier. Else, what would be the point of saying both:
* "contains a valid identifier", and
* "check the validity before the program starts
On Fri, Feb 27, 2004 at 09:27:20PM -0700, John Williams wrote:
: On Fri, 27 Feb 2004, Luke Palmer wrote:
: > John Williams writes:
: > > I want to get from here
: > >
: > > method bar_attr(?$val) is accessor {
: > > $.bar_attr = $val if exists $val;
: > > return $.bar_attr;
: > >
On Sat, Feb 28, 2004 at 02:17:05PM +, Smylers wrote:
(B: Also, not strictly to do with formats but raised by the above, how is
(B: infinity written in Perl 6 (for example, in C<:page{:length($x)}>
(B: how could C<$x> be assigned to infinity)?
(B
(BWhat we've said up till now is that Perl 6
The Exegesis mentions the Perl6::Slurp module, but I don't see it
on CPAN. Is it just a race condition?
Regards,
-- Gregor
--
Gregor Purdy[EMAIL PROTECTED]
Focus Research, Inc. http://www.focusresearch.com/
Gregor N. Purdy writes:
> "...we're guaranteed that the key of the resulting pair is a string,
> that the string [...] contains a valid identifier, and that the
> compiler can check the validity before the program starts."
>
> We aren't told what validity checking the compiler is doing. I figure
Gregor N. Purdy writes:
> In "And now at length they overflow their banks." its not clear
> how an overflow field gets tied to its initial non-overflow field.
> In the recipe example given, how does it know to go with the
> $method field instead of the $prep_time field?
The definition given is:
In "And now at length they overflow their banks." its not clear
how an overflow field gets tied to its initial non-overflow field.
In the recipe example given, how does it know to go with the
$method field instead of the $prep_time field? Is it basing off
of matching the horizontal extent of the in
In "Thou shalt have my best gown to make thee a pair...", we are
given a reason to use the option syntax vs. the pair constructing
fat comma C<< => >>: "...we're guaranteed that the key of the
resulting pair is a string, that the string [...] contains a valid
identifier, and that the compiler can c
In the section "He doth fill fields..." we see an example of Fill
Justification where two spaces fit between every word. This doesn't
give us an idea of how spaces are distributed if the number of
spaces needed does not divide evenly into the number of interstices.
In the section "More particulars
In "From the crown of his head to the sole of his foot..." (clearly
a reference to a Gilligan's Island episode where Lovey said something
similar :), we have:
:header{ ..., odd => "Act, $act, Scene $scene...", ... }
and below, text indicating that it will
"prepend the act and scene infor
First, thanks Damian for doing this, and good show!
Smylers already pointed out a few errors in the document, but
here are a few others I noticed:
* In "Why, how now, ho! From whence ariseth this?"
We have this near the top:
type FormArgs ::= Str|Array|Pair;
and this be
[EMAIL PROTECTED] (Smylers) writes:
> Also, not strictly to do with formats but raised by the above, how is
> infinity written in Perl 6?
â
?
--
even though I know what a 'one time pad' is, it still sounds like
a feminine hygiene product.
[EMAIL PROTECTED] (Smylers) writes:
> Also, not strictly to do with formats but raised by the above, how is
> infinity written in Perl 6?
â
--
Complete the following sentence: People *ought* to weigh bricks, cats
and cinnamon in the same units because... - Ian Johnston
OK, I've given up on having completely separate mails and thrown
together a bunch of small points. Some of these are pointing out typos;
I mention them not to complain, but in case anybody's bothered about
correcting them to avoid future confusion.
* What happens if an undefined format is passe
The C<:page{:length}> sub-option (page 12) is described in the text as
having a default value of infinity but in a comment in the example above
of being 60. How so?
Is that the text normally isn't split into pages at all (so effectively
giving a single page of infinite length), but as soon as C<:
The :fill option gets a brief mention on page 10, but I didn't spot it
anywhere else or being used in an example:
There is also a general C<:fill> option that sets the default sequence
for any filling that isn't otherwise specified.
That suggests there's a hierarchy of options like this:
Praise to Damian for Exegesis 7: the new formats sound very
well-thought-out, flexible, easy-to-use, and extensive -- as well as
being implemented and available right now. I've never used formats in
Perl 5, but I could see myself using Perl6::Form.
I have a few questions. Unfortunately I'm only
40 matches
Mail list logo
