From: Katana <ka...@ka...> - 2004-02-28 10:36:23
|
> the subject with assign accepting arrays just made me start to thing > about api compability to smarty. > > Classes are named using studlyCaps but what about functions? > Still both ways can be found in formsess (get_value(), hasErrors()). > > Since smarty uses underscores in it's function names I vote for doing > that in formsess too. > (Everything else will confuse people, learning formsess is difficult enough) Yes, I know. I have partially fixed that issue, but the big problem now is Backward Compatibility... As far as I'm concerned I'm more a studlyCaps user. It is the pear standard, and I like it better. I know it's not like that in smarty, but there ARE a few things I don't like in Smarty :) Anyway, how would you handle the backward compatibility problem ? Create a method / function with the same name but the chosen convention, and mark the old name as deprecated but keep it working ? Another solution could be a wrapper class with the old function names, so that you can use the whole new ones without having the old ones poluting your memory ? Bertrand |