Re: The new GEDCOM parser

You seem to be mixing two paradigms here: a stream parsing engine 
(having all the callbacks per entity) and a document model builder. I 
recommend to focus on making a solid GEDCOM stream parser (handling 
UTF-8, well-defined grammar). There are many applications that don't 
need to hold all the data in memory.

Once you have a solid *parser*, it's another matter to build object 
models on top of that. The parser is universal functionality. Defining a 
single object model that all consumers will be happy with is an 
impossible task, so you'll be much better served in separating them.


Jeremy


On 11/5/2012 2:36 PM, Ron Savage wrote:
> Still, whatever the data structure chosen, /something/ has to be 
> chosen just to hold the data in memory.