Can anybody explain why the EIT processing in siparser contains all those section trackers & the rest?
Why don't we just 1) Decode event(s) (ParseDVBEIT, ParseATSCEIT etc) 2) Queue event(s) directly into eithelper. After looking for those memory leaks and analysing that code it made me want to get out the hatchet and perform some surgery in that area. Unless there is a good reason I'll start sharpening the hatched :-) Stuart
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
