You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the pattern matcher requires that all things to be searched for have to be given a name, by using a VariableNode or a GlobNode. But this is not really needed: it could be done anonymously, thus making the patterns more compact and a bit easier to read. For example, a current search is of the form:
with the SignatureLink indicating what to look for.
Implementing this should be pretty easy: scan the clauses for SignatureLinks, and under the covers, create a corresponding type VariableNode with some UUID variable name. Do NOT put the variable into the main atomspace; but when the search is to be run, poke it into the transient atomspace, and do the search. ... and pretty much that's it ... everything else runs as before.
This is somewhat related to enhancment request #2599 which scans for variable declarations not in the VariableList ... this is effectively doing the same thing, only it scans for SignatureLinks, and treats them like variables... Huh.
The text was updated successfully, but these errors were encountered:
Sometimes, things do need to be named. In order to say "I want this thing to be the same as that thing", you need to point: either with a finger, or a variable.
combinators
I'm doubtful, having seen them in lambda calculus. But I don't know how one might write graphs in this fashion, maybe something interesting happens.
Anyway, this is maybe part of an effort to sheaf-ify everything. In case its not clear, plugging things into variables is just a special case of connecting together sheaf sections. (I started writing a PDF about this and then got bored.)
Currently, the pattern matcher requires that all things to be searched for have to be given a name, by using a
VariableNode
or aGlobNode
. But this is not really needed: it could be done anonymously, thus making the patterns more compact and a bit easier to read. For example, a current search is of the form:It could be done anonlymously:
with the
SignatureLink
indicating what to look for.Implementing this should be pretty easy: scan the clauses for
SignatureLink
s, and under the covers, create a corresponding typeVariableNode
with some UUID variable name. Do NOT put the variable into the main atomspace; but when the search is to be run, poke it into the transient atomspace, and do the search. ... and pretty much that's it ... everything else runs as before.This is somewhat related to enhancment request #2599 which scans for variable declarations not in the VariableList ... this is effectively doing the same thing, only it scans for SignatureLinks, and treats them like variables... Huh.
The text was updated successfully, but these errors were encountered: