HaloO,
David Green wrote:
On 2008-Oct-22, at 10:03 am, TSa wrote:
Note that types have a fundamentally different task in a signature
than name and position have. The latter are for binding arguments to
parameters. The types however are for selection of dispatch target.
Names do that too; I t
On 2008-Oct-22, at 10:03 am, TSa wrote:
David Green wrote:
One thing I would like signatures to be able to do, though, is
assign parameters by type. Much like a rule can look for
identifiable objects like a or , it would be very
useful to look for parameters by their type or class rather
On Tue, 21 Oct 2008, Timothy S. Nelson wrote:
On Tue, 21 Oct 2008, David Green wrote:
On 2008-Oct-2, at 6:15 pm, Timothy S. Nelson wrote:
The guys on IRC convinced me that the way to go might be something like
a grammar, but that does trees and tree transformations instead of a
text input st
HaloO,
David Green wrote:
One thing I would like signatures to be able to do, though, is assign
parameters by type. Much like a rule can look for identifiable objects
like a or , it would be very useful to look for
parameters by their type or class rather than by name (or position).
For ex
On Wed, 22 Oct 2008, Brad Bowman wrote:
The "scrap your boilerplate" scheme for generics in Haskell addresses
traversals, queries, transformations, parallel zipping and the like.
I've only briefly felt like I understood it, so I was going to
revise before trying to adapt it to Perl 6. (Any lam
The "scrap your boilerplate" scheme for generics in Haskell addresses
traversals, queries, transformations, parallel zipping and the like.
I've only briefly felt like I understood it, so I was going to
revise before trying to adapt it to Perl 6.
(Any lambdacamels out there that do understand th
On Tue, 21 Oct 2008, David Green wrote:
On 2008-Oct-2, at 6:15 pm, Timothy S. Nelson wrote:
The guys on IRC convinced me that the way to go might be something like a
grammar, but that does trees and tree transformations instead of a text
input stream. See the IRC log for details :).
[...]
n
On 2008-Oct-2, at 6:15 pm, Timothy S. Nelson wrote:
The guys on IRC convinced me that the way to go might be something
like a grammar, but that does trees and tree transformations
instead of a text input stream. See the IRC log for details :).
[...]
note to treematching folks: it is envisag
Timothy S. Nelson wrote:
>> note to treematching folks: it is envisaged that signatures in
>> a rule will match nodes in a tree
>>
>>My question is, how is this expected to work? Can someone give an
>> example?
>
>I'm assuming that this relates to Jon Lang's comment about using
>
On Fri, 3 Oct 2008, Timothy S. Nelson wrote:
On Fri, 3 Oct 2008, Timothy S. Nelson wrote:
On Thu, 2 Oct 2008, Timothy S. Nelson wrote:
Now that Perl6 is in the mix, though, I think that the best way to do
it is to make roles that model eg. Nodes, Plexes (Documents), Elements,
and the like,
On Fri, 3 Oct 2008, Timothy S. Nelson wrote:
On Thu, 2 Oct 2008, Timothy S. Nelson wrote:
Now that Perl6 is in the mix, though, I think that the best way to do
it is to make roles that model eg. Nodes, Plexes (Documents), Elements, and
the like, and then have operators on them do all the wor
For tree-oriented pattern matching syntax, I'd recommend for
inspiration the RELAX NG Compact Syntax, rather than XPath.
Technically, RELAX NG is an XML schema validation language; but the
basic principle that it uses is to describe a tree-oriented pattern,
and to consider the document to be valid
On Oct 2, 2008, at 10:36 , Timothy S. Nelson wrote:
On Thu, 2 Oct 2008, Timothy S. Nelson wrote:
Now that Perl6 is in the mix, though, I think that the best way to
do it is to make roles that model eg. Nodes, Plexes (Documents),
Elements, and the like, and then have operators on them do all
On Thu, 2 Oct 2008, Timothy S. Nelson wrote:
Now that Perl6 is in the mix, though, I think that the best way to do
it is to make roles that model eg. Nodes, Plexes (Documents), Elements, and
the like, and then have operators on them do all the work (like my idea of
using a slash for a combine
On Thu, 2 Oct 2008, Daniel Ruoso wrote:
One thing we realized at that time is that XPath is good enough, even if
it seems to be adressing XML specifically, it has the concept of
"dimension" that can be extended to represent arbitrary aspects of
objects.
Hmm. Back in March, before I discovere
15 matches
Mail list logo
