Author: wayland
Date: 2009-02-23 09:42:50 +0100 (Mon, 23 Feb 2009)
New Revision: 25495
Modified:
docs/Perl6/Spec/S16-io.pod
docs/Perl6/Spec/S28-special-variables.pod
Log:
More S28 updates, including turning things into references to elsewhere, and
better
documenting the standard/default
Author: wayland
Date: 2009-02-23 09:52:44 +0100 (Mon, 23 Feb 2009)
New Revision: 25496
Modified:
docs/Perl6/Spec/S32-setting-library/IO.pod
Log:
Fixed a few things based on advice from chrisdolan++
Modified: docs/Perl6/Spec/S32-setting-library/IO.pod
Author: wayland
Date: 2009-02-23 10:32:46 +0100 (Mon, 23 Feb 2009)
New Revision: 25499
Added:
docs/Perl6/Spec/S32-setting-library/Str.pod
Removed:
docs/Perl6/Spec/S32-setting-library/String.pod
Log:
Moved String.pod to Str.pod
Copied: docs/Perl6/Spec/S32-setting-library/Str.pod (from rev
Martin D Kealey wrote:
Ah, we want a noun that isn't readily confused as an adjective.
Suitable terms might include: Instant Jiffy Juncture Moment Occasion Snap Tick
...
Once :)
--
Ruud
Timothy S. Nelson wrote:
On Mon, 23 Feb 2009, Moritz Lenz wrote:
Timothy S. Nelson wrote:
Another question for everyone - is there some way I can extend a class
in such a way that it implements another role?
class A does B does C { ... }
where B and C are roles.
For example, say I
Hi,
Peter Schwenn wrote:
If a class attribute declaration has a . or ! twigil, e.g. has @!items, do
all the ensuing references to @items in the class's methods have to include
the twigil or can the variable be written thereafter simply @items without
the twigil?
If you declare a private
Timothy S. Nelson wrote:
Another question for everyone - is there some way I can extend a class
in such a way that it implements another role?
class A does B does C { ... }
where B and C are roles.
For example, say I have a
class Class::A that implements role Role::A, and I want
HaloO,
Eirik Berg Hanssen wrote:
Suitable terms might include: Instant Jiffy Juncture Moment Occasion Snap Tick
...
Time::Point.
Of course, being Norwegian, I may be biased. ;-)
Same here in German, we have Zeitpunkt which literally means
timepoint. But note that clock time is Uhrzeit
Author: autarch
Date: 2009-02-23 18:49:28 +0100 (Mon, 23 Feb 2009)
New Revision: 25500
Modified:
docs/Perl6/Spec/S32-setting-library/Temporal.pod
Log:
Some fixes to make this valid Perl 6 (returns is out, our RETTYPE is in)
Also some other formatting fixlets
Modified:
Author: bacek
Date: 2009-02-23 21:21:32 +0100 (Mon, 23 Feb 2009)
New Revision: 25501
Modified:
docs/Perl6/Spec/S32-setting-library/Containers.pod
Log:
[spec] Fix typo in map example.
Modified: docs/Perl6/Spec/S32-setting-library/Containers.pod
On Mon, 23 Feb 2009, Ruud H.G. van Tol wrote:
Martin D Kealey wrote:
Ah, we want a noun that isn't readily confused as an adjective.
Suitable terms might include: Instant Jiffy Juncture Moment Occasion Snap
Tick ...
Once :)
Hmm. Temporal::OnceUponATime :).
On Mon, 23 Feb 2009, TSa wrote:
HaloO,
Eirik Berg Hanssen wrote:
Suitable terms might include: Instant Jiffy Juncture Moment Occasion Snap
Tick ...
Time::Point.
Of course, being Norwegian, I may be biased. ;-)
Same here in German, we have Zeitpunkt which literally means
timepoint.
On Mon, Feb 23, 2009 at 4:56 PM, mark.a.big...@comcast.net wrote:
Instant
Most apropos. Classes are nouns, so the adjectival meaning doesn't
cause a conflict, IMHO: an instant has nothing to do with instant
coffee.
Moment
Also apropos, and with a history in the field (Calendrical
Calculations
Author: wayland
Date: 2009-02-24 00:33:42 +0100 (Tue, 24 Feb 2009)
New Revision: 25503
Added:
docs/Perl6/Spec/S14-roles-and-parametric-types.pod
Modified:
docs/Perl6/Spec/S12-objects.pod
docs/Perl6/Spec/S29-functions.pod
Log:
S29: s/Container.pod/Containers.pod/
S14/S12: Extracted S14
Author: wayland
Date: 2009-02-24 01:16:08 +0100 (Tue, 24 Feb 2009)
New Revision: 25506
Modified:
docs/Perl6/Spec/S14-roles-and-parametric-types.pod
docs/Perl6/Spec/S32-setting-library/IO.pod
Log:
IO.pod: Updated reference to Temporal.pod
S14: Gave credits properly
Modified:
I think most forms of IPC should be addons, if only because they have
inherent unportability. Stuff like sockets and pipes should be in
obviously, signals maybe (they have lots of portability issues, but
they may be too often used to just drop), but things like SysV IPC
really shouldn't. Anything
On Tue, Feb 24, 2009 at 1:13 AM, Timothy S. Nelson
wayl...@wayland.id.au wrote:
On Mon, 23 Feb 2009, Leon Timmermans wrote:
I think most forms of IPC should be addons, if only because they have
inherent unportability. Stuff like sockets and pipes should be in
obviously, signals maybe (they
Author: wayland
Date: 2009-02-24 01:42:31 +0100 (Tue, 24 Feb 2009)
New Revision: 25507
Added:
docs/Perl6/Spec/S31-pragmatic-modules.pod
Log:
S31: Collected the pragmata from everywhere, and listed them here with
cross-references
Added: docs/Perl6/Spec/S31-pragmatic-modules.pod
Author: wayland
Date: 2009-02-24 01:53:45 +0100 (Tue, 24 Feb 2009)
New Revision: 25509
Modified:
docs/Perl6/Spec/S16-io.pod
docs/Perl6/Spec/S32-setting-library/IO.pod
Log:
S16: Referred to other documents
IO.pod: Got rid of filetest pragma
Modified: docs/Perl6/Spec/S16-io.pod
On Sun, Feb 22, 2009 at 9:47 PM, pugs-comm...@feather.perl6.nl wrote:
Added: docs/Perl6/Spec/S28-special-variables.pod
===
+=head2 Named variables (see S02):
+$?OS # operating system compiled for
+$*OS
On Mon, 23 Feb 2009, Timothy S. Nelson wrote:
I have a quick question here. S16 claims to be about IPC, IO, and
Signals. So far, it's mostly about IO. My question is, is it intended
that IPC and/or signals be part of the core, or should they be converted
to addons like Form.pm?
On Mon, 23 Feb 2009, jason switzer wrote:
On Sun, Feb 22, 2009 at 9:47 PM, pugs-comm...@feather.perl6.nl wrote:
Added: docs/Perl6/Spec/S28-special-variables.pod
===
+=head2 Named variables (see S02):
+$?OS #
On Tue, Feb 24, 2009 at 04:01:40PM +1300, Martin D Kealey wrote:
: On Mon, 23 Feb 2009, Timothy S. Nelson wrote:
: I have a quick question here. S16 claims to be about IPC, IO, and
: Signals. So far, it's mostly about IO. My question is, is it intended
: that IPC and/or signals be part of
On 2009-Feb-23, at 10:09 am, TSa wrote:
I also think that time and numbers in general should be treated in
a fuzzy way by smart match.
My thought is to have == take a :within adverb, at least for imprecise
types like Num, that could be used to specify how close values need to
come in order
Author: lwall
Date: 2009-02-24 05:36:33 +0100 (Tue, 24 Feb 2009)
New Revision: 25513
Modified:
docs/Perl6/Spec/S02-bits.pod
docs/Perl6/Spec/S03-operators.pod
docs/Perl6/Spec/S12-objects.pod
docs/Perl6/Spec/S16-io.pod
docs/Perl6/Spec/S28-special-variables.pod
Log:
kill DEF* variants
On 2009-Feb-23, Jonathan Worthington posted to Rakudo.org:
Applied a patch from bacek++ to get min= and max= working ($foo
min= 100 will assign 100 to $foo if it's smaller than what is in
$foo).
Nice -- except I first read that backwards, i.e. even though it
follows straight from the
Author: wayland
Date: 2009-02-24 05:56:48 +0100 (Tue, 24 Feb 2009)
New Revision: 25514
Modified:
docs/Perl6/Spec/S19-commandline.pod
Log:
Added a note about @*ARGS
Modified: docs/Perl6/Spec/S19-commandline.pod
===
---
Author: wayland
Date: 2009-02-24 05:57:59 +0100 (Tue, 24 Feb 2009)
New Revision: 25515
Modified:
docs/Perl6/Spec/S32-setting-library/IO.pod
Log:
Added some things taken from the S28 sources.
Modified: docs/Perl6/Spec/S32-setting-library/IO.pod
Author: lwall
Date: 2009-02-24 06:04:42 +0100 (Tue, 24 Feb 2009)
New Revision: 25516
Modified:
docs/Perl6/Spec/S32-setting-library/Any.pod
docs/Perl6/Spec/S32-setting-library/IO.pod
Log:
more DEF extermination
Modified: docs/Perl6/Spec/S32-setting-library/Any.pod
Author: wayland
Date: 2009-02-24 06:10:35 +0100 (Tue, 24 Feb 2009)
New Revision: 25517
Modified:
docs/Perl6/Spec/S28-special-variables.pod
Log:
- Made twigils short (see S02 for full doco).
- Rearranged main variable list
Modified: docs/Perl6/Spec/S28-special-variables.pod
Author: lwall
Date: 2009-02-24 06:13:28 +0100 (Tue, 24 Feb 2009)
New Revision: 25518
Modified:
docs/Perl6/Spec/S28-special-variables.pod
Log:
redelete fossil
Modified: docs/Perl6/Spec/S28-special-variables.pod
===
---
On Mon, Feb 23, 2009 at 09:08:39PM -0700, David Green wrote:
On 2009-Feb-23, at 10:09 am, TSa wrote:
I also think that time and numbers in general should be treated in
a fuzzy way by smart match.
My thought is to have == take a :within adverb, at least for imprecise
types like Num, that
Author: wayland
Date: 2009-02-24 06:17:29 +0100 (Tue, 24 Feb 2009)
New Revision: 25519
Modified:
docs/Perl6/Spec/S28-special-variables.pod
Log:
Lots of general reoganisation. Still needs lots more work, and I will continue
when I get
the chance (probably tomorrow). Hope I haven't
David (), Jonathan on Rakudo.org ():
Applied a patch from bacek++ to get min= and max= working ($foo min=
100 will assign 100 to $foo if it's smaller than what is in $foo).
Nice -- except I first read that backwards, i.e. even though it follows
straight from the definition of [op]=, it made
Larry Wall wrote:
On Fri, Feb 20, 2009 at 03:31:03PM -0300, Daniel Ruoso wrote:
: Em Sex, 2009-02-20 às 10:17 -0800, Larry Wall escreveu:
: By the by, I'm also inclined to agree with those who prefer Instant
: to DateTime on aesthetic grounds.
Yay, I consider that a blessing.
Also yay on
Larry Wall wrote:
snip
This still seems to be confusing implementation issues with the point
I'm trying to make about the basic nature of time.
Duration and Instant are both simple (but typed) Num semantics
on seconds. There are no integers unless you specifically ask for
an interpretation in
36 matches
Mail list logo
