Re: 5.NEXT Integer and String type modifications

Hey :-), On 02/06/13 08:52, Johannes Schlüter wrote:

It would be a *gigantic* patch, but the userland effects should be minimal (the only changes would be supporting longer strings, and consistent 64 bit int support). The performance considerations should be minimal for non-legacy code (as both would still be using native data types)...

History shows that such gigantic patches are often not finished and done as people underestimate the size of PHP and the fact that all etensions have to be checked which for this case means checking each external lib for their correct type for all their functions etc ... but I don't wan to stop you, I'm happy if you do this :-) (while I'm also happy about everybody spending time on fixing bugs instead of adding such high-risk changes ;-)) Is it possible to use a static C analyzer here? It could help a lot. I think about Frama-C [1], Pork [2] (now included in Oink [3]) or Clang Static Analyser [4] to name a few. A more complete list can be found in [5].

The idea is excellent by the way :-). Cheers. [1] http://frama-c.com/ [2] https://developer.mozilla.org/en/docs/Pork [3] http://daniel-wilkerson.appspot.com/oink/index.html [4] http://clang-analyzer.llvm.org/ [5] http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#C.2FC.2B.2B -- Ivan Enderlin Developer of Hoa http://hoa-project.net/ PhD. student at DISC/Femto-ST (Vesontio) and INRIA (Cassis) http://disc.univ-fcomte.fr/ and http://www.inria.fr/ Member of HTML and WebApps Working Group of W3C http://w3.org/