Hi everyone!
In t/src/io.c, specifically test 9 and 10, I wonder if the PIO_eof check up works anywhere; because I didn't manage to find any place where the PIO_F_EOF flag is set up when the PIO_*_open function fails neither in io_stdio.c, io_unix.c nor io_win32.c
In PIO_open the ParrotIO object never gets created if there is an error condition.
PIO_eof() returns true if the PMC has a null IO object or if the PIO_F_EOF flag is set.
Is the "io == NULL" testing prohibited in Parrot embedding system?
0x4c56
Currently it isn't prohibitied. That is the only way to detect an error from PIO_open* at this time.
If someone convinces me that it is better to return a ParrotIO object with error flags set rather than skip creating it, I might consider it.
It is probably more likely that we simply need documentation.
-Melvin
