Thank you beneroth and Joh-Tob for this impressive and insightful
explanation, very informative for me as well, thank you, I will put this on
my PicoLisp notes.
On Thu, Mar 26, 2020 at 8:29 AM Joh-Tob Schäg wrote:
> Have you already looked at the family example?
>
> Here is my brief overview of
Dear Lawrence
Sounds to me that your head got stuffed a bit too well with
over-complicated concepts. No offense! That is the nature of most
software education, and its even worse in the business world. And we
programmers have a high tendency to believe we are more clever when we
are working on
I'm afraid at my level of CS theory I don't really know what is meant by a
picolisp atom being persistent, much less across distributed picolisp
instances. Could someone give me a concrete example of what you describe
as: "Any named bag of items automatically represents a (directed,
undirected)
Lawrence, you haven't yet understood, that any Lisp, by default, is it's
own Graph Database. Especially Picolisp, where Alex has made any Picolisp
Atom persistent and even distributed across other Picolisp instances. 'Data
is code, code is data'.
Any named bag of items automatically represents a
On Fri, Mar 13, 2020 at 10:22:12PM +0100, Alexander Burger wrote:
> Perhaps this helps? https://software-lab.de/doc/tut.html#ext
>
> It is really very simple.
Understanding PicoLisp symbols is perhaps the important point.
https://software-lab.de/doc/ref.html#symbol
The rest is just making
On Fri, Mar 13, 2020 at 04:02:44PM -0500, Lawrence Bottorff wrote:
> Could you point me to a beginner's treatment of this topic, especially an
> example of a graph database, and what exactly a picolisp pointer is?
Perhaps this helps? https://software-lab.de/doc/tut.html#ext
It is really very
Could you point me to a beginner's treatment of this topic, especially an
example of a graph database, and what exactly a picolisp pointer is?
I'm afraid I don't even know what you mean by a pointer in this context. I
know from C what a pointer is, but a picolisp pointer is beyond my
Hi Lawrence,
> I take it the picolisp graph database follows more the Neo4j property graph
> idea than any RDF/OWL triples, correct? That seems obvious, but I thought
> I'd check. I haven't dived in deep, buy you seem to use Lisp objects to
> create a vertex. But then what are the edges? Again,
