On Mon, 14 Jun 2010 14:32:25 +0100, Melanie Rhianna Lewis
wrote:
I know the ANSI C standard pretty well but I don't remember that at all
so rather than just accepting it I checked it on my Mac using a small
example. Compiler details are below:
kring:Development melanie$ gcc --version
i6
2010/6/14 Melanie Rhianna Lewis :
> I know the ANSI C standard pretty well but I don't remember that at all so
> rather than just accepting it I checked it on my Mac using a small example.
> Compiler details are below:
>
> kring:Development melanie$ gcc --version
> i686-apple-darwin10-gcc-4.2.1
I know the ANSI C standard pretty well but I don't remember that at all so
rather than just accepting it I checked it on my Mac using a small example.
Compiler details are below:
kring:Development melanie$ gcc --version
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5657)
In my ex
On Mon, 14 Jun 2010 11:56:57 +0100, Melanie Rhianna Lewis
wrote:
My feeling is that they should all be static consts unless explicitly
accessed outside of the object module or changed.Since typically
they're a list of function/method entries only accessed by a class or
zend_module_entr
My feeling is that they should all be static consts unless explicitly accessed
outside of the object module or changed.Since typically they're a list of
function/method entries only accessed by a class or zend_module_entry that is
really the case. Without the static we're polluting the name
