It's easier to explain with an image:
It should return this:
I first got it with this:
thanks!
I've patched the current dev version with a fix for this:
https://snap.berkeley.edu/versions/dev
Please give it a try (make sure to hard-reload the page to refresh the browser cache) and let me know if you encounter any more issues.
You're welcome.
It works in the dev version now!
This isn't a bug, what you want to accomplish is reifying literals, and I'm not supporting that. You can use unevaluated input slots for that, but - honestly - it doesn't make sense, because literals are just constants that don't closurize an environment.
Ok.
I want it to be something like the Scheme (quote ...), so:
which is exactly what I want it to report.
Edit:
I want to un-reify them, not reify them. (Edit: the block reifies things, but I need the block to know if its input is a literal so it can only then un-reify it)
un-reifying is call. If you want to quote a ring you can ringify the ring.
But what if I have a reporter with a side effect in the input? I don't want any side effects. I only want to un-reify a literal.
Literals in Snap! are text, numbers and Booleans. If you want to extract the body of a function you can now use split for that.
That doesn't help me here, because with this:
it gives this:
but:
I have to have it unevaluated, because:
What I need is how the <is _ a reified literal?> of this:
is supposed to be defined, without Javascript. (I know how to do it with JS, but I want to un-JS-ify it.)
can you give me an example of what you really want to accomplish?
I want to make
in Snap!, as a step towards making macros. This stuff about a block called "QUOTE" was my project. Here.
we'll get around to macros, this is now a first step.
Yes but I want to make some steps myself in the meantime.
geez, and I always thought us Smalltalkers/OOP folks were too full of it 