On 12/15/05, Gaal Yahas <[EMAIL PROTECTED]> wrote:
> What should this mean?
>
> package Foo;
> sub Bar::baz is export { ... }
>
> The problem is in how callers request this export.
>
> use Foo ;
Hmm. My gut reaction is that that is the correct way to request that export.
> Looks w
What should this mean?
package Foo;
sub Bar::baz is export { ... }
The problem is in how callers request this export.
use Foo ;
Looks weird, as this demonstrates:
package Foo;
sub baz is export { "I am Foo::baz" }
sub Bar::baz is export { "I am Bar::baz" }
C
On 12/15/05, Darren Duncan <[EMAIL PROTECTED]> wrote:
> I propose, perhaps redundantly, that Perl 6 include a complete set of
> native
Okay, I'm with you here. Just please stop saying "native" and "core".
Everyone.
Remember, syntax in Perl 6 can be stuffed in a library like anything
else. You
All,
P.S. What follows is rough and will be smoothed out or reworked.
I propose, perhaps redundantly, that Perl 6 include a complete set of
native language constructs for a relational data model, akin to that
introduced in E. F. Codd's classic paper, "A Relational Model of Data
for Large Shar
On Mon, 12 Dec 2005 12:18:47 +1300, Sam Vilain wrote:
> On Thu, 2005-12-08 at 17:16 +0100, Ron Blaschke wrote:
>> The Free Lunch Is Over: A Fundamental Turn Toward Concurrency in Software."
>> [1] He starts with "The biggest sea change in software development since
>> the OO revolution is knocking
Two and a half years ago, Fotango announced their sponsorship of the Perl
6 effort, in the form of the "Ponie" project to port the Perl 5 runtime to
the Parrot Virtual Machine. For the past year, Nicholas Clark has worked
as the pumpking for Ponie as part of his work for Fotango. He's recently
move
