3 ms·
> I think the problem can be solved though if the development environment shows the stack at each point in time; that way the computer does the thinking instead
by innguest 12y ago
> I think the problem can be solved though if the development environment shows the stack at each point in time; that way the computer does the thinking instead of the programmer.
If you're up for it I have some code that I wrote with this very idea in mind, in Factor. I'll put it on github later today and put the link here anyway. I agree with you 100%. If Factor were transparent that way and interactive that way (to the point it's almost like a dialog, which it already almost is with its Listener but you and I want stack transparency) then it would probably be one of the most productive languages for fast prototyping (at least).
- bcheung 12y agoI'd be curious to take a look. I have plans to do something similar but in the browser in Javascript. Basically, build up the AST based on the commands that are issued against the stack. Then use the Mozilla Parser API to generate Javascript code. Additionally, with the example arguments supplied you have test driven develop built right in. Not only do you get tests, but it helps you visualize things as you program.
- innguest 12y agoSorry for the delay: https://gist.github.com/anonymous/6ec7128c10e9ea1f63ad https://gist.github.com/anonymous/6ec7128c10e9ea1f63ad I agree with you 110%, in fact I can't understand why this hasn't been done yet.