the parse code blocks seem inaccurate...
Just an edge case where the encoded text of both blocks is the same.
does snap do anything against this?
oh
Hmm, that seems like a bug, or a misfeature or something.
The problem is, the lisp code does not contain any information about block shape or input types, it just uses the block label.
yep, it's because the block label is ambiguous if there are several blocks sharing it. If you only have one it works fine:
Hmm, maybe the "Lisp code" feature should augment the block label with, say, a two-letter code whose first letter would be C for Command, R for Reporter, or P for Predicate and whose second letter would be the category name. Or, for the sake of translations, make it a number whose integer part is [0-2] and whose fraction part is the category number.
the Lisp code is not about the shape of blocks or inputs - there also isn't any distinction between commands and reporters - just about names.
Yes, I see that! That's why I said "should." :~) Perhaps I'm not understanding the point of the feature; it doesn't help me that the output isn't, in fact, much like Lisp code, so the help text doesn't help me. Did you invent this with an application in mind? (You've probably already told me this, but we've already established that I have no memory for anything more recent than 1982.)
we've talked and exchanged messages / mails about this in extenso. We need this so we can mix Snap code into the JS code for bootstrapping the alternative Snap code for primitives. We cannot load external files because of the JS sandbox, so we have to include the Snap code in the JS sources. That's the purpose of this. Also, it lets us extend Snap way more easily with human readable (and editable!) text files, including hooking up to generative AI features such as CoPilot. It is not a wonder weapon for this folks of this forum.
[edit] you've reviewed the Lisp code specs before the release and I've implemented all your change requests
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.