Nico Edtinger
2008-01-17 18:37:47 UTC
We still have the newline problem in Zend_Mime. The current task is
ZF-1886. It was changed from \r\n to \n, which is not standard, but
fixed some problems. Now others have problems and want it to change
from \n to \r\n, which is more correct, but would again raise the
issue we fixed the last time. It's a lose:lose situation and it breaks
in some kind backwards compatibility.
nico
ZF-1886. It was changed from \r\n to \n, which is not standard, but
fixed some problems. Now others have problems and want it to change
from \n to \r\n, which is more correct, but would again raise the
issue we fixed the last time. It's a lose:lose situation and it breaks
in some kind backwards compatibility.
nico
That should be A-OK. Only changes that could potentially break
existing
applications would be a BC issue.
,Wil
existing
applications would be a BC issue.
,Wil
-----Original Message-----
Sent: Thursday, January 17, 2008 7:05 AM
Subject: Re: [fw-general] 1.5 and backwards compatibilty. . .
changed
the method name, however it was previously declared as private thus I
suppose there's no BC issue here.
--
View this message in context: http://www.nabble.com/1.5-and-
backwards-
compatibilty.-.-.-tp14915193s16154p14921159.html
Sent from the Zend Framework mailing list archive at Nabble.com.
Sent: Thursday, January 17, 2008 7:05 AM
Subject: Re: [fw-general] 1.5 and backwards compatibilty. . .
*If you have made an API or behavior change for 1.5 that is not
backwards compatible, please notify me ASAP.*
In order to fix http://framework.zend.com/issues/browse/ZF-1308 Ibackwards compatible, please notify me ASAP.*
changed
the method name, however it was previously declared as private thus I
suppose there's no BC issue here.
--
View this message in context: http://www.nabble.com/1.5-and-
backwards-
compatibilty.-.-.-tp14915193s16154p14921159.html
Sent from the Zend Framework mailing list archive at Nabble.com.