Re: Call for Votes: JSON location
| From: | Pierre | Date: | Fri, 07 Apr 2006 22:29:48 +0000 |
| Subject: | Re: Call for Votes: JSON location | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-42133@lists.php.net to get a copy of this message | ||
On 4/8/06, Joshua Eichorn <josh@bluga.net> wrote:
> For my use in HTML_AJAX not at all, but im not sure how, you would fit
> that into the pear packaging standards, or if you really would want too.
The name of the package and what it provides may differ. I do not see
a problem to have JSON or (Services|HTML|Text)_JSON as name and the
two public methods in one file.
> Since even if you wrapped it in functions_exists you don't have a good
> way of guaranteeing that the c code and the php code output the same thing.
> Of course this is mainly a problem on the decode where you have to make
> choices about using assoc arrays or objects
The output must be semantically the same. As far as I know they work
together to keep both sync'ed.
> I'd expect you'd want the code in PEAR to match the extension but i
> don't know how easy of a job that is too do. My extent of working with
> the code has been patching around utf-8 encoding problems.
It is not an easy job, but even a nearly compatible version (> 90%) is
way more usefull than a OO interface, from a maintenance and forward
compatibility point of view.
--Pierre