I agree with just about everything you wrote. I only have two minor
quibbles and they may merely be restatements of what you meant.
--- Rob Kinyon [EMAIL PROTECTED] wrote:
Overriding the operators in a generic way so that you have
to have an exact type match before you compare values also,
On 12/16/05, Ovid [EMAIL PROTECTED] wrote:
Minor nit: we're discussing to the relational algebra and not the
relational Calculus (unless the topic changed and I wasn't paying
attention. I wouldn't be surprised :)
Algebra, in general, is a specific form of calculus. So, we're
speaking of the
At 2:54 AM + 12/15/05, Luke Palmer wrote:
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.
Yes, of course. What I meant
As an addendum to what I said before ...
The general kind of thing I am proposing for Perl 6 to have is a
declarative syntax for more kinds of tasks, where you can simply
specify *what* you want to happen, and you don't have to tell Perl
how to perform that task.
An example of declaratives
On Dec 15, 2005, at 2:19, Darren Duncan wrote:
* a Tuple is an associative array having one or more Attributes,
and each Attribute has a name or ordinal position and it is typed
according to a Domain;
this is like a restricted Hash in a way, where each key has a
specific type
* a
Darren Duncan schreef:
If you take ...
+-+-+
|a|x|
|a|y|
|a|z|
|b|x|
|c|y|
+-+-+
... and divide it by ...
+-+
|x|
|z|
+-+
... the result is ...
+-+
|a|
+-+
I'm not sure if Divide has an equivalent in SQL.
A verbose way to do it:
SELECT
Darren Duncan wrote:
As an addendum to what I said before ...
...
I would want the set operations for tuples to be like that, but the
example code that Luke and I expressed already, with maps and greps etc,
seems to smack too much of telling Perl how to do the job.
I don't want to have to
[snip entire conversation so far]
(Please bear with me - I'm going to go in random directions.)
Someone please correct me if I'm wrong, but it seems that there's only
a few things missing in P6:
1) An elegant way of creating a tuple-type (the table, so to speak)
2) A way of providing
Ruud H.G. van Tol schreef:
[RD-interface]
See also these Haskell Hierarchical Libraries (base package)
http://www.haskell.org/ghc/docs/latest/html/libraries/base/Data-Set.html
http://www.haskell.org/ghc/docs/latest/html/libraries/base/Data-Map.html
--
Affijn, Ruud
Gewoon is een tijger.
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
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.
rant
Remember, syntax in Perl 6 can be stuffed in a library like anything
else. You
Perl 6 Summary for 2005-12-05 through 2005-12-12
All~
Welcome to another Perl 6 summary. This week, like last, Parrot has
produced the highest volume of emails. Fine by me, Parrot tends to be
easiest to summarize. This summary is brought to you by Snow (the latest
soft toy
On Nov 23, 2005, at 3:06, chromatic wrote:
On Wed, 2005-11-23 at 01:39 +0100, Leopold Toetsch wrote:
But my argument was: whenever you
start introspecting a call frame, by almost whatever means, this will
keep the call frame alive[1] (see Continuation or Closure). That is:
timely destruction
On Nov 22, 2005, at 1:40, Matt Fowles wrote:
Call Frame Access
Chip began to pontificate about how one should access call frames.
Chip
suggested using a PMC, but Leo thought that would be too slow.
No, not really. It'll be slower, yes. But my argument was: whenever you
start
On Wed, 2005-11-23 at 01:39 +0100, Leopold Toetsch wrote:
But my argument was: whenever you
start introspecting a call frame, by almost whatever means, this will
keep the call frame alive[1] (see Continuation or Closure). That is:
timely destruction doesn't work for example...
Destruction
Perl 6 Summary for 2005-11-14 through 2005-11-21
All~
Welcome to another Perl 6 Summary. The attentive among you may notice
that this one is on time. I am not sure how that happened, but we will
try and keep it up. On a complete side note, I think there should be a
Perl guild
On Tue, 15 Nov 2005, The Perl 6 Summarizer wrote:
Perl 6 perlplexities
Michele Dondi worries that the increase in complexity of some aspects of
Perl 6 is much bigger than the increase in functionality that the
complexity buys us. In particular Michele is concerned that the Perl 6
On Mon, 24 Oct 2005, H.Merijn Brand wrote:
FEAR: Perl6 will not be able to fix the stigma of just a scripting
language or line noise
perl5 has never been just a scripting language
But sadly enough it is often _perceived_ as such. And also like line
noise, as the person you're answering to
. But if you want me to discuss things beforehand, people better be
reachable and responding, because I generally lose interest if I don't
get started within a few days. That kind of thing has been a problem
with other projects, and I love how Perl 6 development is so open and
free, focussed on fun
On 10/24/05, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Mon, 24 Oct 2005 11:49:51 -0400, Joshua Gatcomb [EMAIL PROTECTED]
wrote:
FEAR: Perl6 internals will be just as inaccessable as p5
paradox. Many people don't find perl5 inaccessible at all
Who? Do you know anybody who hacks the regex
On 10/25/05, Luke Palmer [EMAIL PROTECTED] wrote:
On 10/24/05, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Mon, 24 Oct 2005 11:49:51 -0400, Joshua Gatcomb [EMAIL PROTECTED]
wrote:
FEAR: Perl6 internals will be just as inaccessable as p5
paradox. Many people don't find perl5 inaccessible
On Tue, Oct 25, 2005 at 11:57:10AM -0600, Luke Palmer wrote:
On 10/24/05, H.Merijn Brand [EMAIL PROTECTED] wrote:
On Mon, 24 Oct 2005 11:49:51 -0400, Joshua Gatcomb [EMAIL PROTECTED]
wrote:
FEAR: Perl6 internals will be just as inaccessable as p5
paradox. Many people don't find perl5
=head1 Perl 6 Summary for 2005-10-10 through 2005-10-18
All~
Welcome to another Perl 6 Summary. Sadly, this week's summary is not
brought to you by cookies as I already finished them. Sadder still,
it is also brought to you a week late. On the plus side, Mike
Doughty's Haughty Melodic
Matt Fowles [EMAIL PROTECTED] wrote:
=head3 Obsolete Win32 Exports
Michael Walter found and removed some obsolete Win32 Exports.
Jonathan Worthington applied the patch. Weren't we planning on auto
generating these?
The Plan is to mark functions that are to be exported with something that
The current list of fears is:
You don't include my personal fear.
FEAR: I will need a lobotomy before I can make sense of Perl 6!
--
Stop the infinite loop, I want to get off! http://surreal.istic.org/
Paraphernalia/Never hides your broken bones,/ And I don't know why you'd
want to try
Here is my part.
On Oct 24, 2005, at 07:20 , Juerd wrote:
I've created pugs/docs/quickref/fears, a list of Perl 6 fears.
Feel free to add your own, or fears you heard about!
[snip]
: FEAR: Perl 6 has too many operators!
FEAR: Perl 6 has so many operators that it runs out of Unicode
Feel free to add your own, or fears you heard about!
Fear: Perl 6 will not attract enough interested developers and
companies to gain momentum. People will continue to be excited about
digital watches and PHP 5.
Regards,
Christian
--
[EMAIL PROTECTED] - http://christian.web42.com - http
Christian Renz wrote:
Feel free to add your own, or fears you heard about!
Fear: Perl 6 will not attract enough interested developers and
companies to gain momentum. People will continue to be excited about
digital watches and PHP 5.
I think Perl 6 will take time to insterest developers
On 10/24/05, Juerd [EMAIL PROTECTED] wrote:
Feel free to add your own, or fears you heard about!
FEAR: Perl6 internals will be just as inaccessable as p5
FEAR: The Perl6 process is driving away too many good developers
FEAR: Perl6 will not be as portable as p5
FEAR: Perl6 will not be able
want Perl 6 to be the community's rewrite
of Perl and of the community. - Larry Wall
I think a lot of people that would contribute, myself included, are put off
by the fact that it is nearly impossible to get a clear decision rendered on
the list. Threads spin off tangents and typically end
On Mon, Oct 24, 2005 at 02:47:58PM +0100, Alberto Manuel Brandão Simões wrote:
Another is because it will take too long to port all CPAN modules to
Perl 6 (for this I suggest a Porters force-task to interact with current
CPAN module owners and help and/or port their modules).
I think
I fear that, at age 70, I shall not live long enough to become efficient with
perl 6.
Two full years ago I purchased and read Perl 6 Essentials. That lead me to
this list which I have enjoyed but never felt competent to contribute much.
Pretty much all of what I leaned in Essentials has been
Joshua Gatcomb wrote:
On 10/24/05, Juerd [EMAIL PROTECTED] wrote:
Feel free to add your own, or fears you heard about!
FEAR: The Perl6 process is driving away too many good developers
FEAR: Perl6 will not be as portable as p5
FEAR: Perl6 is un-necessary and the time, money, and resources
On 10/24/05, Nate Wiger [EMAIL PROTECTED] wrote:
Joshua Gatcomb wrote:
On 10/24/05, Juerd [EMAIL PROTECTED] wrote:
Feel free to add your own, or fears you heard about!
FEAR: The Perl6 process is driving away too many good developers
FEAR: Perl6 will not be as portable as p5
FEAR:
the same time Perl 6.0.0 comes out
there's still plenty of time ;-)
On Fri, 14 Oct 2005 22:11:18 +0200 [EMAIL PROTECTED] wrote:
I'd like to start by saying DON'T PANIC! I'm not going to write a
book on Perl 6 ;-)
Luckily we have people with much more enlish-fu,
structured-thought-fu
On Oct 15, 2005, at 7:39 AM, Rutger Vos wrote:
Good idea. A fat new O'reilly tome will go some way to capturing
mind share
for perl6. Gathering ideas wiki-style is also very Web2.0. Perhaps
perl6
could be marketed as such, what with the development style -
Perl6, the
first Web2.0
On Oct 15, 2005, at 9:57 AM, David Storrs wrote:
I would suggest we avoid trying to link Perl6 with Web2.0 in
people's minds, at least at first. One of the uphill battles that
I'm really tired of fighting is convincing people that Perl is good
for more than CGIs and quick-n-dirty system
I'd like to start by saying DON'T PANIC! I'm not going to write a
book on Perl 6 ;-)
Luckily we have people with much more enlish-fu,
structured-thought-fu, and general get-it-done-fu... Now let's talk
a bit about them:
Today Geoff Broadwell raised a book idea for discussion on #perl6
On Oct 5, 2005, at 1:17, Matt Fowles wrote:
Here Doc in PIR
Will Coleda revived a thread from February about PIR here doc
syntax.
Looks like the syntax is ok.
Jonathan Worthington has already implemented here doc syntax.
Data::Escape::String Dislikes Unicode
Will
Perl 6 Summary for 2005-09-26 through 2005-10-02
All~
Welcome to another summary, this time a day late because I was in Philly
for Serenity. If you haven't seen Serenity yet you should stop reading
this summary and go see it. The summary will be here when you get back.
I
Perl 6 Summary for 2005-09-12 through 2005-09-19
All~
Welcome to another Perl 6 Summary, this time brought to you with a
shorter pause (::grumble:: $WORK ::grumble::) and assisted by cookies.
Perl 6 Compilers
Circular Preludes for Fun and Confusion
Yuval Kogman posted
On Mon, Sep 05, 2005 at 08:29:00PM +0100, Nicholas Clark wrote:
It's not valid perl 4:
$ perl4 -e 'no 5; print [EMAIL PROTECTED]'
syntax error in file /tmp/perl-em47tij at line 1, next 2 tokens no 5
Execution of /tmp/perl-em47tij aborted due to compilation errors.
$ perl1 -e 'no 4; print
On Mon, Sep 05, 2005 at 12:35:36PM +0900, Dan Kogai wrote:
And I found that these can be made much, much simpler and more
intuitive with Perl 6, even more so than scheme!
our $ZERO = sub($f){ sub($x){ $x }};
our $SUCC = sub($n){ sub($f){ sub($x){ $f.($n.($f)($x)) }}};
our $ADD
(Sorry for replying _so_ late...)
On Tue, 9 Aug 2005, Larry Wall wrote:
I kinda like Autrijus's idea that meta just means guts. In
classical Greek, meta just means with. The fancy philosophical
meaning of aboutness isn't there, but is a backformation from
terms such as metaphysics.
On Thu, Sep 01, 2005 at 12:07:59PM -0500, David Nicol wrote:
Does this mean that we have to implement perl4 compatability?
perl5 -e 'no 5; print [EMAIL PROTECTED]'
It's not valid perl 4:
$ perl4 -e 'no 5; print [EMAIL PROTECTED]'
syntax error in file /tmp/perl-em47tij at line 1, next 2
;
$n-($m) }};
And I found that these can be made much, much simpler and more
intuitive with Perl 6, even more so than scheme!
our $ZERO = sub($f){ sub($x){ $x }};
our $SUCC = sub($n){ sub($f){ sub($x){ $f.($n.($f)($x)) }}};
our $ADD = sub($m){ sub($n){ sub($f){ sub($x){ $m.($f
On 9/1/05, Rafael Garcia-Suarez [EMAIL PROTECTED] wrote:
I just commited into bleadperl a patch that implements this :
$ ./perl -e 'no 5'
Perls since v5.0.0 too modern--this is v5.9.3, stopped at -e line 1.
BEGIN failed--compilation aborted at -e line 1.
That is, the exact
in mind for it is to put no 6 at the top of
modules or programs that are too tightly bound to Perl 5 that there
wouldn't be beneficial to port them to Perl 6. B::* or Safe come to
mind. Of course, that would mean that Perl 6 should also recognize and
handle the no 6 idiom. That's why I'm cc:ing p6l
HaloO Larry,
you wrote:
: we need only provide an alternate comparison to
: the constructor, and the set itself needn't remember it. On the
: other hand, hashes behaving like mutable sets need to remember their
: comparison operator if it is not the default.
:
: The slot accessor paradigma
Hi,
What is the correct way to do pass through args?
In perl 5 we would do:
sub whatever {
...
nested_call(@_);
...
}
but slurpy args are undesireable, since they are lossy:
data loss - shape of input parameters is
On Aug 28, 2005, at 5:52 AM, Yuval Kogman wrote:
On Sun, Aug 28, 2005 at 05:18:42 -0400, David Storrs wrote:
On Aug 28, 2005, at 5:12 AM, Yuval Kogman wrote:
On Sun, Aug 28, 2005 at 05:02:25 -0400, David Storrs wrote:
nested_call.wrap(), maybe?
It's not 100% the same thing... Wrapping is
On Sun, Aug 28, 2005 at 05:18:42 -0400, David Storrs wrote:
On Aug 28, 2005, at 5:12 AM, Yuval Kogman wrote:
On Sun, Aug 28, 2005 at 05:02:25 -0400, David Storrs wrote:
nested_call.wrap(), maybe?
It's not 100% the same thing... Wrapping is for wrapping only. This
applies to super methods,
On Sun, Aug 28, 2005 at 05:02:25 -0400, David Storrs wrote:
nested_call.wrap(), maybe?
It's not 100% the same thing... Wrapping is for wrapping only. This
applies to super methods, delegate methods, and so forth.
--
() Yuval Kogman [EMAIL PROTECTED] 0xEBD27418 perl hacker
/\ kung foo
On Aug 28, 2005, at 5:52 AM, Yuval Kogman wrote:
oops... Can I forward our correspondence to the mailing list?
Sure. I was wondering why you took it private. :
--Dks
time exports
Runtime exports
Well, all exports happen at compile-time, but you're right, some exports
(regular subs) will probably not be used before runtime.
Excuse my stupid question, but what about the equivalent Perl 6 case to
the following.
use Module qw{symbol};
BEGIN {
die
point.
I don't know how this is dealt with WRT to the every module is
compiled with it's own compiler approach perl 6 is supposed to
have.
When compiling modules the compiler can seperate out stuff that will
modify the caller's enviroment (exports ect) and thouse that will
not.
When use is seen
On Wed, 24 Aug 2005 16:13:03 +0300, Yuval Kogman [EMAIL PROTECTED] wrote:
[...]
perl6 creates a new instance of the perl compiler (presumably an
object). The compiler will only compile the actual file 'foo.pl',
and disregard any 'require', 'use', or 'eval' statements.
use has the potentional
perl 6 is supposed to
have.
Autrijus - do you have any solution?
Either way, this simply implies that compilation is recursive, at
least to determine whether the used module affects compilation.
Perhaps the use macro could do this on it's own.
I still think that regular linkage should be decoupled
On Aug 25, 2005, at 7:16 AM, David Formosa (aka ? the Platypus) wrote:
On Wed, 24 Aug 2005 16:13:03 +0300, Yuval Kogman
[EMAIL PROTECTED] wrote:
[...]
perl6 creates a new instance of the perl compiler (presumably an
object). The compiler will only compile the actual file 'foo.pl',
and
compiler approach perl 6 is supposed to
have.
The indermediate form of a compiled .pm has to have a section containing
information about the symbols exported by the module, similar to
today's pilGlob section Pugs gives you if you use -CPIL, -CPerl5, or
-CJSON:
$ pugs -CPerl5 -we 'sub foo
On Thu, Aug 25, 2005 at 15:42:28 +0200, Ingo Blechschmidt wrote:
This section will contain all information needed:
* User-defined operators
* Other symbols exported by is export
* Exported macros
Okay, this raises a distinction:
Compile time exports
Runtime exports
Modules
Hi,
Yuval Kogman wrote:
On Thu, Aug 25, 2005 at 15:42:28 +0200, Ingo Blechschmidt wrote:
This section will contain all information needed:
* User-defined operators
* Other symbols exported by is export
* Exported macros
Okay, this raises a distinction:
Compile time exports
Runtime
to the every module is
compiled with it's own compiler approach perl 6 is supposed to
have.
It's pretty simple, really. If module A uses module B, then you go
and compile B first. Then, when you get to use B in module A, you
just call B::import at compile time.
That is, the modules are compiled
WRT to PIL and compilation and all that, I think it's time to think
about how the linker might look.
As I see it the compilation chain with the user typing this in the
prompt:
perl6 foo.pl
perl6 is a compiled perl 6 script that takes an input file, and
compiles it, and then passes
On Aug 23, 2005, at 3:43, Matt Fowles wrote:
Perl 6 Summary for 2005-08-15 through 2005-08-22
Java on Parrot
I vote for Jot.
That's already occupied by another language
http://en.wikipedia.org/wiki/Iota_and_Jot.
Perl 6 Language
Type Inferencing in Perl 5
Autrijus
On Mon, Aug 22, 2005 at 09:43:41PM -0400, Matt Fowles wrote:
Java on Parrot
Tim Bunce asked some preliminary questions about Java on Parrot. I
provide preliminary answers, and Nattfodd and Autrijus posted links to
related work. The important question of what it should be
Perl 6 Summary for 2005-08-15 through 2005-08-22
All~
Welcome to another monday summary, which hopefully provides some
evidence that mondays can get better. It always feels like writing
summaries is an uphill battle, perhaps I should switch to writing about
Perl 6 Language
On Thu, Aug 11, 2005 at 01:35:14AM +0800, Autrijus Tang wrote:
On Wed, Aug 10, 2005 at 07:32:01PM +0200, TSa wrote:
you wrote:
Perl 6 in its unannotated form is also (mostly) a typeless languages,
with only the five builtin types, much like Perl 5 is.
Counting the sigil quadriga as 4
HaloO,
Larry Wall wrote:
[..] but since sets are
immutable values,
Does that imply they travel in $vars and are a subtype
of Value? Is Undef of Set the Set::Empty? Is Set::Empty false?
we need only provide an alternate comparison to
the constructor, and the set itself needn't remember it.
On Fri, Aug 12, 2005 at 04:30:09PM +0200, TSa wrote:
: HaloO,
:
: Larry Wall wrote:
: [..] but since sets are
: immutable values,
:
: Does that imply they travel in $vars and are a subtype
: of Value?
I believe so.
: Is Undef of Set the Set::Empty?
I don't think so. The empty set should
On 8/10/05, Dave Rolsky [EMAIL PROTECTED] wrote:
[changing the subject line for the benefit of the summarizer ...]
On Wed, 10 Aug 2005, Larry Wall wrote:
And now some people will begin to wonder how ugly set values will look.
We should also tell them that lists (and possibly
Luke Palmer wrote:
On 8/10/05, Dave Rolsky [EMAIL PROTECTED] wrote:
[changing the subject line for the benefit of the summarizer ...]
On Wed, 10 Aug 2005, Larry Wall wrote:
And now some people will begin to wonder how ugly set values will look.
We should also tell them that lists (and
Mark A. Biggar wrote:
Luke Palmer wrote:
On 8/10/05, Dave Rolsky [EMAIL PROTECTED] wrote:
[changing the subject line for the benefit of the summarizer ...]
On Wed, 10 Aug 2005, Larry Wall wrote:
And now some people will begin to wonder how ugly set values will look.
We should also tell
On Thu, Aug 11, 2005 at 08:25:23PM -0700, Mark A. Biggar wrote:
: Mark A. Biggar wrote:
: Small issue, what comparison operator do you use to determine
: duplicates? For example (possibly pathological case):
:
: (undef but true) (+) (undef but false)
:
: Actually, I'm going to make a stab at
Larry Wall skribis 2005-08-09 16:19 (-0700):
So either something in the context tells us what Foo means, or
it will be taken as a list operator that hasn't been declared yet.
Is there, by the way, a pragma to force predeclaration of subs, to gain
compile time typo checking?
Juerd
--
, the visibility of an
autoloader turns off this compile-time error checking.
We can get away with this in Perl 6 because bindings to positionals
happen lazily. So all we have to check for syntactically is that we
don't have a subsequent declaration that changes the syntax from list
to unary (or none-ary
On Wed, Aug 10, 2005 at 10:12:45AM -0700, Larry Wall wrote:
We can get away with this in Perl 6 because bindings to positionals
happen lazily. So all we have to check for syntactically is that we
don't have a subsequent declaration that changes the syntax from list
to unary (or none-ary
HaloO,
Luke Palmer wrote:
On 8/10/05, TSa [EMAIL PROTECTED] wrote:
Here is an example of a 2D distance method
role Point
{
has Num $.x;
has Num $.y;
}
method distance( Point $a, Point $b -- Num )
{
return sqrt( ($a.x - $b.x)**2 - ($a.y - $b.y)**2);
}
[..]
# This
HaloO Autrijus,
you wrote:
Perl 6 in its unannotated form is also (mostly) a typeless languages,
with only the five builtin types, much like Perl 5 is.
Counting the sigil quadriga as 4, what is the fifth element?
And $it.does(LookGood)?
--
$TSa.greeting := HaloO; # mind the echo!
On Wed, Aug 10, 2005 at 07:32:01PM +0200, TSa wrote:
you wrote:
Perl 6 in its unannotated form is also (mostly) a typeless languages,
with only the five builtin types, much like Perl 5 is.
Counting the sigil quadriga as 4, what is the fifth element?
@ $ % ::
In Perl5, :: is replaced
HaloO,
Larry Wall wrote:
It might be a mistake to call these isa relationships though. I really
only care about
Package does Object.
Module does Package.
Role does Module.
Class does Role.
OK, I've added that and the Set type in my little type lattice.
With your Object still
[changing the subject line for the benefit of the summarizer ...]
On Wed, 10 Aug 2005, Larry Wall wrote:
And now some people will begin to wonder how ugly set values will look.
We should also tell them that lists (and possibly any-junctions)
promote to sets in set context, so that the usual
Perl 6 Summary for 2005-08-02 through 2005-08-10
All~
Welcome to another summary, brought to you by chinese food. The
attentive among you will notice that this summary is a day late, because
I did not feel like doing it yesterday. If only I could do that at
work...
Perl 6
Stevan,
Up until today, I thought I had a good idea of how your metamodel
works, but now I'm confused. My main sticking point is that a class
Foo seems to have three different aspects:
Foo
class(Foo)
meta(Foo)
For each of these, could you please try to explain:
1) Roughly what its
Guten Tag Herr Sandlaß,
On Aug 9, 2005, at 4:48 AM, TSa (Thomas Sandlaß) wrote:
HaloO,
Stevan Little wrote:
Here is a 10,000 ft view of the metamodel prototype I sketched out
the other day
(http://svn.openfoundry.org/pugs/perl5/Perl6-MetaModel/docs/
10_000_ft_view.pod). It should shed a
HaloO,
Stuart Cook wrote:
So far, this is what I have picked up; some/most of it is probably wrong:
At least your confusion matches nicely with mine :)
~ Foo ~
Is a type that variables etc. can be declared to have
Is not an object
= I'm really not sure about this...
Bare Foo is a
HaloO Stevan,
you wrote:
Guten Tag Herr Sandlaß,
you know that a formal German greeting in a collequial
environment can be interpreted as unfriendly? I don't
do that but just wanted to state the fact.
The next level where a 1:n relation exists is below meta(Foo) to pure
meta.
Not
uglier or
more verbose or some such.
Perl 6 in its unannotated form is also (mostly) a typeless languages,
with only the five builtin types, much like Perl 5 is.
I suspect that the unannotated form will be the form most program
begins, which is why they are (naturally) shorter than annotated forms
Stuart,
On Aug 9, 2005, at 9:25 AM, Stuart Cook wrote:
Stevan,
Up until today, I thought I had a good idea of how your metamodel
works, but now I'm confused. My main sticking point is that a class
Foo seems to have three different aspects:
Foo
class(Foo)
meta(Foo)
For each of these, could
On Aug 9, 2005, at 12:36 PM, TSa wrote:
HaloO Stevan,
you wrote:
Guten Tag Herr Sandlaß,
you know that a formal German greeting in a collequial
environment can be interpreted as unfriendly? I don't
do that but just wanted to state the fact.
My apologies, no unfriendliness intended :)
The
On Aug 9, 2005, at 10:52 AM, TSa wrote:
~ Foo ~
Is a type that variables etc. can be declared to have
Is not an object
= I'm really not sure about this...
Bare Foo is a namespace lookup.
Yes, TSa is right. Everything below this is Type-stuff and I will leave
that to him (up until the
for class(Foo).
Well, Perl 6 The Language sees Foo as package(Foo), actually.
: This is all, of course, implementation details.
When Perl 6 The Language sees any bare identifier, it cannot treat
it as a bareword like Perl 5 does, since Perl 6 has no barewords.
So either something in the context
'Foo', at least not in the metamodel. 'Foo' is a magical
: interpreter concept, which is really just an
: alias/pointer/level-of-indirection/whatever for class(Foo).
Well, Perl 6 The Language sees Foo as package(Foo), actually.
IIRC, autrijus said that one of the base concepts in PIL
Hello All,
Since autrijus is now busy porting the P5 metamodel prototype into
Haskell for use in Pugs, I have decided to begin work on documenting
the Perl6::MetaModel prototype modules more thoroughly. The first step
I see in this is to define a Meta Object Protocol (aka - the stuff you
can
Coming in late here, but it seems odd to have an actual class called
MetaClass. The meta-object protocols with which I am familiar have the
concept of a metaclass (a class whose instances are themselves classes), and
the class Class is such a metaclass, but where does a class named MetaClass
fit
Mark,
On Aug 8, 2005, at 4:26 PM, Mark Reed wrote:
Coming in late here, but it seems odd to have an actual class called
MetaClass. The meta-object protocols with which I am familiar have
the
concept of a metaclass (a class whose instances are themselves
classes), and
the class Class is
HaloO,
in case someone might be interested, here is my more or less complete
idea of the Perl 6 type lattice as ASCII art.
Enjoy. Comments welcome.
::Any
Perl 6 Summary for 2005-07-19 through 2005-07-26
All~
Welcome to another Perl 6 Summary brought to you by microwaved chinese
food and air conditioning. I love the modern era. Without further ado, I
bring you
Perl 6 Compilers
Grégoire Péan announed the release of PxPerl
Hi All,
Being a relative newcomer to all that is Perl 6, can someone tell me what
differences
I need to know in order to write/amend Perl 6 extension Modules as opposed
to
Perl 5 versions ?
I have downloaded PXPerl for Windows (which seems a bit broken to me atm)
and
wanted to start writing
On Thu, Jul 14, 2005 at 12:14:57PM -0600, John Williams wrote:
: Actually I took his question to be:
:
: If I explicitly name my invocant in the method signature, does that give
: the compiler enough assurance that I'm not going to use .method to mean
: $?SELF.method, and it will allow me to
801 - 900 of 1442 matches
Mail list logo
