The nuance of cross-referencing these calls between two .cpp files (listed
in
config.m4, and so compiled into distinct .o files), eludes me.
It's a c/cpp grammar issue, I guess, but one I've never had to deal with
till
now.
Quick Lesson:
static: Symbols (functions, variables, etc...) declar
Hi there,
I've successfully developed a stripped down C++ php class creator,
with private storage, a la Marcus Boerger util.c, and following Jay Smith,
George Schlossnagle et al.
For neater code, I've stripped out function declarations, function entry
tables, class entry etc. into a second .h/.c
Please review my attempt [0] to reimplement the output control code and make
your opinion, support or objections public. A patch [1] to try, the API [2]
and the actual code [3] are online for review. There's alse a README [4]
explaining the what-why-how.
Remaining issues:
- Getting rid of
Hi,
I am wondering why does defining a php5 style and php4 style constructor
in a class result in an E_STRICT warning, where as only defining a php4
style constructor does not?
class foo {
function __construct() {}
function foo() {}
}
class foo2 {
function foo2() {}
}
I could
Translating the PHP documentation to Dutch.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
