> On Solaris with Sun CC, however, I've had to manually edit the
> Makefile or the libtool script in order to successfully build
> my extension. When I compile the extension into PHP, I have to
> change $(CC) to $(CXX) in certain places in the Makefile.
*.cpp files are automatically compiled u
>
>Add PHP_REQUIRE_CXX to your config.m4
Thanks for the reply, but I've already got PHP_REQUIRE_CXX in my config.m4, and I'm
setting the
cxx flag in PHP_NEW_EXTENSION. Is there anything else I'm missing?
- Mark
>--Jani
>
>
> On Tue, 19 Aug 2003, Mark Spruiell wrote:
>
>>I've written a P
Add PHP_REQUIRE_CXX to your config.m4
--Jani
On Tue, 19 Aug 2003, Mark Spruiell wrote:
>I've written a PHP5 extension in C++ that builds great on Linux with GCC, whether I
>compile it
>into PHP or build it as a shared library.
>
>On Solaris with Sun CC, however, I've had to ma
Hello.
I think that it would be useful to allow an __autocreate() function create
non-existing
variables just like __autoload is called for non-existing classes. The
function will be
called when an attempt is made to read a non-existent variable. It will
return a reference
to the new variable it cr
I've written a PHP5 extension in C++ that builds great on Linux with GCC, whether I
compile it
into PHP or build it as a shared library.
On Solaris with Sun CC, however, I've had to manually edit the Makefile or the libtool
script in
order to successfully build my extension. When I compile the e
On Tue, Aug 19, 2003 at 05:32:41PM -0500, Shaun Thomas wrote:
> > > 2.) variable_exists can not be written in PHP.
> >
> > And it is not necessary, because get_defined_vars() exists.
>
> Which is just plain gross, but let's continue on...
How many local variables do you have? That array shouldn'
On Wed, 20 Aug 2003, Stefan Walk wrote:
> Won't work.
> [EMAIL PROTECTED]:~$ php -r 'var_dump(isset($var) || is_null($var));'
>
> Notice: Undefined variable: var in Command line code on line 1
> bool(true)
Ah yes. I was writing from the perspective of having set a value to
null beforehand. M
On Tue, Aug 19, 2003 at 04:38:03PM -0500, Shaun Thomas wrote:
> On Tue, 19 Aug 2003, fabrice wrote:
>
> > Empty($var) ? DoSomethingIfNotSetOrNull() : DoOther();
>
> That won't work. empty() will return true if the variable is set to a
> literal zero, false, blank, or null. So for your use, it's
On Tue, 19 Aug 2003, fabrice wrote:
> Empty($var) ? DoSomethingIfNotSetOrNull() : DoOther();
That won't work. empty() will return true if the variable is set to a
literal zero, false, blank, or null. So for your use, it's actually
worse than isset assuming your data can have zeros or blank val
You're doing something wrong then, as it has worked for others. A
configure line would help to debug this.
On Tuesday, August 19, 2003, at 10:38 AM, nucleuz wrote:
Hi!
I'm running OSX 10.3 ( Panther ) and the snaps fails to compile.
I got the Panther seed at the WWDC earlier this year, and t
Hi!
I'm running OSX 10.3 ( Panther ) and the snaps fails to compile.
I got the Panther seed at the WWDC earlier this year, and there are
newer seeds out, but I don't have that
yet so I don't know if it will compile on that one.
( My C skills are rather limited, but here is what I have trying to
You may consider to use "empty" function that check if isset and not NULL
And also "!empty" inverse function.
Empty($var) ? DoSomethingIfNotSetOrNull() : DoOther();
Also it is true, I use a personnal function to check var ...
Something like that
Function variable_exists( $var )
{
$retur
At this stage it is already too late for patches for the 4.3.3 release. You
can still commit your patch to HEAD (PHP 5.0) and MFH it to PHP_4_3, but you
should know that the fix will not be part of the 4.3.3 release. Pending any
critical issues 4.3.3 will be released based upon RC4.
Ilia
. Pl
On Tue, 19 Aug 2003, Corne' cornelius wrote:
>I have a patch for the Informix extensions that fixes a bug which is
>quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416,
>16145, 14314).
>Can i commit this to the PHP_4_3 branch and can it be included in
>PHP-4.3.3 final ?
>
>or
On Tue, 19 Aug 2003, Corne' cornelius wrote:
> I have a patch for the Informix extensions that fixes a bug which is
> quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416,
> 16145, 14314).
> Can i commit this to the PHP_4_3 branch and can it be included in
> PHP-4.3.3 final ?
Hi,
I have a patch for the Informix extensions that fixes a bug which is
quite old, but a big problem (Related bugs: 13459, 8267, 14254, 19416,
16145, 14314).
Can i commit this to the PHP_4_3 branch and can it be included in
PHP-4.3.3 final ?
or do i need to commit it to PHP_4 now, and to PHP
16 matches
Mail list logo
