Actually no, from the PIO routines you should return a PMC that has a null handle, or that was my original intent. I think I was considering changing new_io_pmc() to return something like ParrotUndef in that case but never did. The very first version of the IO routines actually did return NULL for every error, but it was decided that wasn't the cleanest way.
If you look at the revision history of io.c, revision 4673, I commented:
>> Bug fixes. We should not be returning NULL for io PMCs, that generates an exception now.. A PMC should be returned with a NULL ParrotIO * for valid eof/bool tests. << As this was 2003, I honestly don't remember all of the discussion.
There might be a record of it between Dan and me in the archives, however, chances are it was on IRC.
-Melvin
At 07:44 AM 5/5/2005, Leopold Toetsch wrote:
Luke Palmer <[EMAIL PROTECTED]> wrote:
> This patch makes PIO_fdopen return NULL when you give it flags it > doesn't understand. I gathered that this was the correct behavior > from the test that I untodid.
> Luke
Thanks, applied. leo
