Status: Stdio fixes and improvements

Carl Sassenrath, CTO
REBOL Technologies
26-Oct-2009 18:12 GMT

Article #0281
Main page || Index || Prior Article [0280] || Next Article [0282] || 8 Comments || Send feedback

Here's a quick status update...

With major parse improvements implemented, please report any remaining bugs in CureCode so we can get them fixed. Please do not post reports for features that are not intended to be part of 3.0.0. (Minimize the noise on CureCode.) See the Parse Project wiki document, which you can edit if needed.

For the last few days the development focus is on fixing standard I/O (stdio), I/O redirection, proper UTF-8 for redirection, and the echo function. These may seem fairly simple, and it's not much code, but there are quite a few variations, all of which must be validated and tested.

Here's the list of what's involved...

  • lower level boot output (turned off in current builds)
  • boot crash notification (OS dependent)
  • higher level boot output (what you normally see)
  • lower level trace output
  • console prompt output
  • console input
  • PRINT function output
  • INPUT function input
  • system/port/output
  • system/port/input
  • echo output

Most of these are implemented, but the system/port changes are still pending.

I suppose I should also ask if you want stderr output. I'm not sure I see the need for it, and stderr can confuse the output stream. But perhaps you have a good reason for it?

Today effort is going into writing tests that will run on all platforms to validate that these work. Once stable, I'll post the tests (a script that builds all the tests, which are shell scripts themselves). I'll also be posting the R3 C code related to this. It's clean and easy to read.


Updated 12-Jun-2024 - Edit - Copyright REBOL Technologies -