quote:
k, some questionary on the rules (reading them now):
-do we need to verify that the file indeed is PxM image?
If it is not a PxM image then you can't display it and you might need to return an appropriate error code. Covered in the "Inputs & Outputs" section.
quote:

-what level of error reporting we need to have? I mean, do we need to check error after each pixel and stuff?
That is entirely up to you, however, the rules say, if you can't display it (for any reason) then an appropriate error code needs to be returned.
quote:

-do we need to check for open file handle or can we just open any handle?
Again, if you can't display the image, then return the error code
quote:

-can there be whitespace in the file BEFORE the header?
According to the file format defnition, the first two bytes of the file are the "magic identifyer" Px with 0<x<7.
quote:

-do we need to close anything? like can we leave the files open etc.
Whaty happens if I run 15 images through the test suite? [Razz]
quote:

-how well we should scan the files for whitespace?
as example, the feep-file could be 100k in size with a lot of whitespace in midst of it. should we code around this?
The way I read the PxM definitions, they alwasy talk about a single whitespace as delimiters as they never use the plural of whitespace in anything.
_________________________
There are two types of vessels, submarines and targets.