Changes

From Genome Analysis Wiki
Jump to navigationJump to search
no edit summary
Line 12: Line 12:  
** This allows calling code to set that option and then not have to check for failures since the code it calls would abort on a failure.
 
** This allows calling code to set that option and then not have to check for failures since the code it calls would abort on a failure.
 
** Could/should this be achieved using exceptions?  User can decide to catch them or let them terminate the program.
 
** Could/should this be achieved using exceptions?  User can decide to catch them or let them terminate the program.
*SamFile add a constructor that takes the filename and a flag to indicate open for read/write. (abort on failure to open)
+
*<S>SamFile add a constructor that takes the filename and a flag to indicate open for read/write. (abort on failure to open)</s>
** Also have 2 subclasses one that opens for read, one for write: SamReadFile, SamWriteFile?  Or SamFileRead, SamFileWrite?
+
** <S>Also have 2 subclasses one that opens for read, one for write: SamReadFile, SamWriteFile?  Or SamFileRead, SamFileWrite?</s> <span style="color:blue">- went with SamFileReader and SamFileWriter</span>
 
* Add a function that says: skipInvalidRecords, validateRecords, etc.
 
* Add a function that says: skipInvalidRecords, validateRecords, etc.
 
** That way, ReadRecord will keep reading records until a valid/parseable one is found.
 
** That way, ReadRecord will keep reading records until a valid/parseable one is found.

Navigation menu