15:47:18Bike(though your sed syntax is wrong, Oh No!!)
15:53:25devonjackdaniel: Your graph at https://common-lisp.net/project/ecl/static/quarterly/img/vol4/all-hierarchy.png implausibly shows Lisp-to-C --> Star Sapphire
16:09:43devonJackDaniel: lol, according to a list of Commercial Common Lisp implementations at https://www.cs.cmu.edu/Groups/AI/html/faqs/lang/lisp/part4/faq-doc-2.html ... Star Sapphire Common LISP 3.4 ... Sapiens Software also has a Lisp-to-C translator in beta-test
16:16:54jackdanielso that means that I didn't made a mistake there?
16:19:55devonI'd guess the ...> arrow points the wrong way as SSCL is a complete product and I don't know whether the later Lisp-to-C product ever made it out of Beta.
16:21:27jackdanielI don't think Lisp-to-C translator has some code from Star Sapphire, if it is the component of the latter
16:22:02jackdanielso I'd say the direction is right here
16:23:07devonArrows normally indicate time and SSCL precedes Lisp-to-C
16:24:48devonSSCL is an interpreter written in C. Most likely Lisp-to-C is written in SSCL
16:26:00jackdanielarrows are not about timeline, note clasp <--> ecl (even if clasp is ecl's fork)
16:26:07jackdanielmany changes has been backported
16:27:23devonOk, if not ancestry, what do the arrows indicate?