That is the first step :), if you have a decent text editor, you could add a real print-it or do-it token, which is not regarged as source code, but just as meta information. I think we could quite easily do this in Amber right now ;).
But yes, why not, sounds like a reasonable idea to put print-its and compilation errors in double quotes. On 2013-10-18, at 14:59, [email protected] wrote: > > Just a random idea flitting thought my mind... When trying to <Accept> some > code with an error in it, the error message gets inserted into the code such > that it screws up syntax highlighting and also you need to use <Undo> to > remove it. I wonder if the error might be inserted between double-quotes > making it a comment. The same could be said for if you <PrintIt> from a > debugger. It seems such a simple and obvious idea that I presume its been > considered before and there are good reasons not to do it. I am curious what > others think might be the pros/cons of it. > In the case of <PrintIt> one benefit might be that the code could still be > saved, with the result left as a kind-of example. This might be good for > temporary code development in a Workspace. > > cheers -ben >
signature.asc
Description: Message signed with OpenPGP using GPGMail
