Quote:
I don't understand why [...] the proper function?
Had to be changed... didn't have to be changed... does it make a difference? I'm honestly not sure about the details myself, but the source as I posted it pacifies a few compilers--preventing warnings and in one case an error.
Quote:
I still don't get [...] before outputting something?
It seems that it is basically the "minibasic" variation of the C++ stream `width' functionality.
Quote:
The problem with that [...] seems to have vanished.
True, but it would still be faster than the current approach. Don't worry about it for now, I'll see what I can do with this as my next pass.
Quote:
Trivial (it was actually implemented in the source I pushed yesterday).
^_^
Quote:
Not sure what I was thinking there.
*shrug*
I may have been the one to do it the first place.
Quote:
We can probably just [...] setting for the visibility.
Better. Much better...
Quote:
the huge number of calls [...] to support multiple variants.
Agreed. The instance should be stored in a member and set once in the constructor. If nothing else, if we clean that up now if/when we are able to move to a different implementation that isn't an implicit singleton we will already have the relevant portions of the source free of such issues.
Quote:
But shouldn't it also [...] may need a little reworking.
See my notes within the source... I just don't know what to set the `split' variable to or what logic to apply for text. And now that I'm sure what it does, if not the exact expectations, we really need to rename `split' to something more illustrative.
Quote:
I'm willing to take a vote on that, but I [...] switching to a "HAS A" design.
In my opinion, the class should be a member of the various classes that depend on it.
Quote:
But you can't have multiple consoles, can you?
That depends exclusively on the platform, and I do hope to have a GUI eventually.
Quote:
Come to think of it, it might [...] a sense it "IS A" console.
You could argue this for the current design, but this is solely because the class functions as glue between various other classes.
I would say that the class is an interface to a console, but not the console itself.
Quote:
And we certainly shouldn't really [...] do you think?
If I manage to port my syntax highlighting over we would, in a way, have three. (At the least, three clients of the class.)
Quote:
Inheriting certainly will [...] that there is a pointer stored somewhere.
*shrug*
There is also my hopes of having a GUI eventually. Of course, more primitives would be available to a GUI so it could be two different "minibasic" classes, but that strikes me as a wrongheaded approach to something that can be done without inheritance.
Soma