[wp-hackers] Returning instead of echoing

Owen Winkler ringmaster at midnightcircus.com
Thu Nov 11 21:13:13 UTC 2004


Ryan Boren wrote:
> On Thu, 2004-11-11 at 13:20 -0700, Alex King wrote:
> 
>>IMO - Sweeping changes that break existing functionality aren't good 
>>candidates for a point release.
> 
> 
> Backwards compatibility must be and will be preserved.  And if by point
> release you mean 1.3, 1.3 is hardly a point release any more.  It's our
> biggest release yet, I reckon.  Might as well call it 2.0.
> 
> But, point taken.  Perhaps we should limit changes of this type to only
> those get_*() functions that people have been begging for as well as
> those that are preventing proper i18n.  comment_type() is an example of
> both cases.  We need get_comment_type().

So far I've only scratched the surface of feasibility for the changes.

The next step should be to see what functions might break existing 
functionality if they're pushed toward the new formatting, and then 
figure how to avoid that - aka The Hard Work.

The logic for doing all of them is the same as the logic for doing only 
some.  Better not to pick only what looks important, and just see what 
it takes to do them all.

Is anyone else thinking of taking this on, or am I doing it?

Owen




More information about the hackers mailing list