On 04/29/2015 07:54 AM, Andrew Dalke wrote: > I don't have a good solution. Were it me, I would have the writer > fail should any unsupported value be present in the output, > including those which are allowed by the SD specification but will > cause problems in practice, like embedded "\0" and leading "$$$$".
Based on "be liberal in what you accept and conservative in what you produce", the writer should > - convert multiple newlines into one (including the edge cases) - > also enforce the 200 character restriction - also enforce a check for > well-known legal but ill-advised character sequences - if a record contains forbidden values, stop writing to the file, with an error. With the reader it looks like you can't help it if someone makes a value like "> 55" or "$$$$". With that caveat, you should be able to find tags and read everything in between as a value. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Rdkit-discuss mailing list Rdkit-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rdkit-discuss
