On Oct 21, 2010, at 4:46 AM, Fred Ludlow wrote: > For what I'm doing I can live with both of those, so I think I'll try doing > it this way first - if it works and you think having disconnected matching's > worth the extra layer of parsing and possible matching inefficiency it should > be possible to alter OBSmartsPattern so that internally it instantiates > several sub OBSmartsPatterns, not that that' a very beautiful way of doing > it... but anyway, I'll try and get it working without touching the core > parsmart code first.
Well, there's definitely a way to bridge the two approaches, now that you mention it. OBSmartsPattern::Init() can handle the special case where "." is found in the pattern, and either pass the pieces to an internal OBDisconnectedSmarts class or handle the pieces itself. I'm going to go add a private data class to OBSmartsPattern to make this possible. -Geoff ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ OpenBabel-Devel mailing list OpenBabel-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-devel
