Slava Pestov <[EMAIL PROTECTED]> wrote: > This would be a good approach if the csv parser had an alternative > entry point taking an array of strings.
Personally, I'd think a stream/pipe processing API would be more general. That would work both with your comment/csv mashup, and with a more complex mashup where the two components don't always agree on what a "record" is (for example, one adding SQL statements onto a C syntax, or one adding C++ comments into an old C parser). The point is that both CSV and # comments have the same idea of when a record ends -- the end of the current line. In general that neat coincidence doesn't hold. > Slava -Wm ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
