Do we know anything about the actual lineage of Lego Logo? Is it derived from some other Logo implementation?
It's derived from the M.I.T. original version. The university's Media Lab and Lego were well-documented collaborators (and still are).
The reason I ask is because at least with Apple Logo there are hooks implemented for assembly language (at least according to page 238 of http://www.virtualapple.org/docs/Apple%20Logo%20II%20Reference%20Manual.pdf)
It's possible that such hooks also exist for Lego Logo if it were derived from some less child-oriented implementation (i.e. present in the upstream but not documented in Lego's docs).
Devin
Great find... how about switch to Apple Logo and extend it with machine language to use that hardware? That could be WAY more practical. DC
Whoa! Devin/Doug: I was talking to Dean tonight about a similar concept. Lego provided a BASIC program for the IBM and LOGO for the Apple, so we figured if we use the BASIC/IBM then we might be able to know the status of a given port on the interface box (which is the problem I want to solve). Dean said he thinks that's a good idea vs. trying it in Lego LOGO where we lack assembler access. It added that it still may depend on whether the Lego BASIC card keeps a signal status when a port is on/off, because if it only sends a toggle then we're back to square one. However, neither of us thought of rolling our own "VCFed LOGO" :) (which I like a lot better than using BASIC, as the meta point of this application is to teach little kids and I'm unsatisfied with the limitations of the Lego LOGO implementation). It seems inefficient to start with ordinary Apple LOGO, add all the Lego LOGO stuff, and then add the (ahem) Evan LOGO addition, vs. taking what Lego already added and then tacking on what I want, but I totally understand why you're both suggesting it this way. Dean, you're my main man on this subject, what do you think?