EDS and Memory
I was going to reply to Philip's post, but Federico did a wonderful job before I could start.
That said, I still haven't forgiven you for some of the finer details of libecal Federico. :)
Posted by Federico Mena-Quintero at Wed Mar 19 22:04:36 2008:
Yeah, the design was a bit clunky... and I blame libical for that :)
Back then there wasn't stuff like ical_get_summary(event); you had to iterate through all the event's properties and look for the "SUMMARY" one by hand. So, CalComponent was the high-level interface I wrote to do that kind of stuff.
And the memory management was always screwed up in libical... it looks like it's finally getting cleaned up.
(CalComponent also had some semi-nice code to deal with some of the complexities of iCalendar, such as when to increment the fucking sequence numbers in events... apps would have a hard time being compliant without that knowledge being centralized somewhere.)
Posted by Ross at Wed Mar 19 22:31:44 2008:
Back then there wasn't stuff like ical_get_summary(event); you had to iterate through all the event's properties and look for the "SUMMARY" one by hand. So, CalComponent was the high-level interface I wrote to do that kind of stuff.
And the memory management was always screwed up in libical... it looks like it's finally getting cleaned up.
(CalComponent also had some semi-nice code to deal with some of the complexities of iCalendar, such as when to increment the fucking sequence numbers in events... apps would have a hard time being compliant without that knowledge being centralized somewhere.)
