(Responding to 3 notes on 2 mail lists here; Changed subject line.)
Juerd wrote:
> Feather, the semi-public, semi-private, Perl 6 development server, is
> available to host a Perl 6 wiki.
>
> The hostname www.perl6.nl is deliberately kept available for something
> like that.
Does that mean you a
The (oh so very cool) idea of implementing the perl 6 wiki IN perl 6
(eventually) is a powerful argument. I also concede that control
issues mean we don't want the official wiki to be on wikipedia. Kwiki
is already a perl-based wiki, but I have no experience using it. We
don't have to put perl 6 u
Please, for proper threading, don't reply to multiple messages at once.
Conrad Schneiker skribis 2006-05-25 1:46 (-0700):
> Juerd wrote:
> > Feather, the semi-public, semi-private, Perl 6 development server, is
> > available to host a Perl 6 wiki.
> > The hostname www.perl6.nl is deliberately ke
Author: larry
Date: Thu May 25 11:21:16 2006
New Revision: 9307
Modified:
doc/trunk/design/syn/S06.pod
Log:
Clarifying the distinction between the "of" and "where" return types.
Modified: doc/trunk/design/syn/S06.pod
===
Larry pointed out that this topic is better suited for perl6-language instead
of perl6-users, so I'm forwarding this along. Feel free to exercise your
"delete" key.
Cheers,
Ovid
-- If this message is a response to a question on a mailing list, please send
follow up questions to the list.
W
Hmm...
How about this:
Treat each knowledge base as an object, with at least two methods:
.fact() takes the argument list and constructs a prolog-like fact or
rule out of it, which then gets added to the knowledge base.
.query() takes the argument list, constructs a prolog-like query out
of it,
[EMAIL PROTECTED] wrote:
>+In either case this sets the C property of the container to C.
>+Subroutines have a variant of the C property, C, that
>+sets the C property instead. The C property specifies
>+a constraint to be checked upon calling C that, unlike the C
>+property, is not advertized as
