Patrick,
I'd prefer the 2nd way. However let me have a
look first to get an impression about
implications.
Regards,
Beat
Hello!
I'm currently testing with a libical which generates VTIMEZONE
information with \r\n line endings. A while ago (Tue Apr 21 09:21:17
2009 +0200) I already fixed the extraction of the VTIMEZONE NAME. I must
have missed at that time that extracting the other information from such
a VTIMEZONE also fails because BEGIN:STANDARD\n and BEGIN:DAYLIGHT\n is
not found.
I'm now a bit torn about how to fix this. The brute-force approach is to
replace \r\n \n\r and \r with \n to at the start of VTIMEZONEtoTZEntry()
and keep the rest of the code as it is. But that wouldn't fix other
callers of VStr(), which is a globally visible function.
The other approach is to change VStr() and VPeeledStr() so that they
work with arbitrary line ends. Any thoughts on this?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
--
-----------------------------------------------
Beat FORSTER
Dipl. El. Ing. ETH
Dipl. NDS ETHZ in Betriebswissenschaften
Managing Partner
[email protected]
Synthesis AG SyncML Server & Client Solutions
Badenerstrasse 18, CH-8004 Zürich, Switzerland
Tel (direct): +41 44 440 66 02
Fax: +41 44 440 66 04
email: [email protected]
web: http://www.synthesis.ch
-----------------------------------------------
_______________________________________________
os-libsynthesis mailing list
[email protected]
http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
