O_oThe user edits the line and [...] the line number over and over.
That's what the edit feature is for...
*shrug*Neither the console nor [...] minibasic and minibasic::interpreter.
The `interpreter' spawns a `compiler'...
*shrug*I think a better candidate for history navigation might [...] keys, personally.
But then you wouldn't be modeling today's text editors...
As far as modern editors go, do any modern C++ editors wrap lines by default?
Correction... the interpreter...As I pointed out earlier, the compiler knows nothing about minibasic.
No. It doesn't. The design or the implementation as it stands may need to spawn a new instance to deal with the "INPUT" function, but the function itself can be implemented without needing another `compiler' or `interpreter'.In fact, the only reason [...] to do it's work.
Having the queue feature be a part of the interface exported from the `console' class doesn't break encapsulation nor does it change its usefulness to outside classes. In fact, even as the source stands, it would probably take changing a grand total of six lines, only two in "console.cpp", to support what I'm suggesting and use it.I disagree. Being part of the [...] of the input history feature.
Actually, the callback mechanism that handles ESCAPE uses a singleton. It just doesn't directly access a singleton.Only minibasic and minibasic::interpreter [...] as they *use* these objects.
We are using global state everywhere.
There is nothing but unnecessary intermingling. We've only decorated bad C in the guise of C++. As far as usability, reliability, and expandability goes the current implementation is almost as bad as the single source C++ file you guys had long ago and not much further from the original assembler.The point is, there is no unnecessary intermingling here, whatsoever.
We obviously disagree on this. I've helped you guys track down a few bugs. I've added a few bits and cleaned up a few things. I assumed we were trying to get a working version so we knew what we needed. I can only imagine that you'll want to continue the design in a similar vein or let it stagnate and rot with other poorly punned hacks. I admit, I am the who wrote the worst ones, but still I think I'll return to working on other projects in the time allotted for this project.
Of course, if you guys find a bug you just can't nail I'll be happy to take a look.