Blockland Forums > General Discussion
RTB Dedicated Hosting Service
Kalphiter:
--- Quote from: Trinick on November 16, 2012, 06:56:02 PM ---Then you're doing a horrible job wrapping a program.
--- End quote ---
Who needs to see that?
Trinick:
--- Quote from: Kalphiter on November 16, 2012, 07:21:07 PM ---Who needs to see that?
--- End quote ---
Nobody. That's not the point. The point is you usually don't want to break functionality of the program so rerouting anything would be a bad choice. The better choice would be to listen for the software interrupt.
Kalphiter:
--- Quote from: Trinick on November 16, 2012, 08:27:46 PM ---Nobody. That's not the point. The point is you usually don't want to break functionality of the program so rerouting anything would be a bad choice. The better choice would be to listen for the hardware interrupt.
--- End quote ---
Why would you complicate it?
Trinick:
I wouldn't call that a complication, I'd call it doing it the right way. It's not complicated at all, just wait for the interrupt then grab the string off the stack.
M:
--- Quote from: Trinick on November 16, 2012, 08:27:46 PM ---Nobody. That's not the point. The point is you usually don't want to break functionality of the program so rerouting anything would be a bad choice. The better choice would be to listen for the hardware interrupt.
--- End quote ---
If Torque's console itself wasn't so ungodly loving horrid it wouldn't break anything.
Fun fact: That windows console window you see with Blockland is not actually a console or terminal. It's part of Torque. It doesn't listen to stdin - it captures keystrokes instead, and does all the printing itself. It still appears even if its output is rerouted somewhere else, unlike basically any other program.
Nothing is broken by wrapping the stdout from the console, at least no more so than it already was.