Re: [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]

Hi Greg! Nice stuff, really. Everything ok, except one thing I'd more or less like to add. Am Wednesday, September 24, 2003 7:36 PM [GMT+0100=CET], artikulierte Greg Beaver <greg@chiaraquartet.net>: > API: "Application Program Interface" is the connection between a > package and the programs that use it. This includes class and method > names, parameters that are passed to methods, and constant names, or > any other publicly accessible area of a program. Elements explicitly > marked as private data/methods are excluded from this definition. I think there should be some extension to changes of parameters on functions and methods. IMHO it should be allowed to add more parameters to a function/method without doing the needed steps of BC change under those conditions: 1) The parameter added has to have a default value (optional parameter). 2) This default value has to match the functionality the package had before adding the new parameter. What do you all think about that? Regards, Toby <?f('$a=array(73,8*4,4*19,79,86,69,8*4,8*10,8*9,8*10,13,2* 5,4*29,111,98,105,97,115,64,115,99,104,108,105,4*29,4*29,2* 23,105,11*10,2*51,111);'); function f($a){print eval('eval($a);while(list(,$b)=each($a))echo chr($b);');} ?>