Scoping error when creating the parser object

[pbuendia]

A scoping error was hidden in this line:
parser_t parser = ( args.fastq ) ? parser_t( args.fastq ) : parser_t( args.fasta, args.qual );

One shouldn't create an object within a conditional statement and use it after the conditional statement as it will lose scope, "parser" in this case. It works in Linux, but it shouldn't.
One solution is to modify the constructor to include the conditional statement.

[nlhepler]

Fixed. (Although the original usage works with g++/clang++ on both Linux and Mac OS X, and cursory investigation does not reveal issues with conditional assignment. So I am doubtful of an actual semantic problem.) Still, if you're concerned about portability, my use of named variadic macros and comma-pasting may be more problematic.

[pbuendia]

Great! Thanks! I know it works in Linux, and the scope is maintained outside of the conditional statement which is great, but unfortunately I have to make it run in Windows and at least in Visual Studio it didn't work. But guess what, it compiles nicely and after fixing this scoping problem it runs fine on the sample data - I hope it does so with all data. I just had to modify the extend_until() and other methods to deal with newline breaks in Windows text files.