Wait a sec... When did const become a keyword? And since when can you
initialize variables from outside a constructor/function?
Sorry to bother..
--
// DvDmanDT
MSN: [EMAIL PROTECTED]
Mail: [EMAIL PROTECTED]
"Zeev Suraski" <[EMAIL PROTECTED]> skrev i meddelandet
news:[EMAIL PROTECTED]
> At 14:35
On Sat, 23 Aug 2003, Melvyn Sopacua wrote:
>ext/standard/dns.c includes arpa/nameser.h if HAVE_ARPA_NAMESER_H is defined.
>Can you check config.h for this?
>
>(By the way: the win32 version tests for HAVE_ARPA_NAMESERV <-- the 'v' here -
>is that a typo?)
---8<-:dns.c
#if HA
At 14:35 22/08/2003, Arjen Brouwer wrote:
Should'nt this work? Currently it reports an error about a undefined constant.
Should be var $bar = Test::FOO (or self::FOO, even though it appears not to
work right now) - there's no implicit class/object dereference of any kind
in PHP.
Zeev
--
PHP In
Hi,
firstly: 10.3 is still beta, AFAIK.
So, they might wise up.
On Tuesday 19 August 2003 16:38, nucleuz wrote:
> I then did a grep for T_MX and found this in 'nameser8_comap.h'
> When doing
> #include
Apparently OSX has imported Bind9 into the main source and decided to do their
own thing. T
> Mark Spruiell wrote:
>>
>> Unlike GCC, Sun's C and C++ compilers are independent entities, therefore
>> you can't link a C++ program or shared library when the C compiler is
>> driving the linker. It's also not possible to compile PHP's C code with
>> Sun's C++ compiler.
>>
>> I guess we're a lit
Mark Spruiell wrote:
>
> Unlike GCC, Sun's C and C++ compilers are independent entities, therefore
> you can't link a C++ program or shared library when the C compiler is
> driving the linker. It's also not possible to compile PHP's C code with
> Sun's C++ compiler.
>
> I guess we're a little spo
>
> fwiw, I've never had these problems with gcc's C++ compiler on Solaris when
> building C++ extensions, and the final linking step is usually done by gcc,
> not g++. When you do the linking, do you link to the stdc++ library?
Unlike GCC, Sun's C and C++ compilers are independent entities, there
>> 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 com
Shane Caraveo wrote:
> try reverting that patch in your build and see if it fixes your
> problem.
My problem gets already fixed by building Release_TS_Inline instead of
Debug_TS.
Rob can possibly elaborate a bit more on this, I think.
--
Sebastian Bergmann
http://sebastian-bergmann.de/
"Arjen Brouwer" <[EMAIL PROTECTED]> escreveu na mensagem
news:[EMAIL PROTECTED]
> Should'nt this work? Currently it reports an error about a undefined
constant.
>
> class Test {
> const FOO = 100;
> var $bar = FOO;
> }
>
> $Test = new Test;
> echo $Test->bar;
> ?>
>
> Ciao,
> Arjen
>
IMHO
Sebastian Bergmann wrote:
Sebastian Bergmann wrote:
Using the current CVS of PHP 5's SAPI/CGI on Windows I get the
following message for every script
No input file specified.
I investigated a bit and found out that this broke between August, 4th
and August, 5th, meaning that
cvs upd -D
(I'm sending this to the internals list partly in the hope that
an experienced Zend/extension developer will take a quick
look over my code and point out any obvious mistakes I've
made ;)
This is a prelimiary release of a PHP interface to libical.
Libical is a C library that can read/modify/write
On Fri, 22 Aug 2003, Gareth Ardron wrote:
> I've got an extension which was written for 4.1/4.2, and everything worked
> great. I've just (by accident of me not paying attention to an apt-get
> dist-upgrade) upgraded to 4.3.2 and I can't get the extension to compile now.
> I keep getting bitchi
Should'nt this work? Currently it reports an error about a undefined constant.
bar;
?>
Ciao,
Arjen
It's also broken in the PHP_4_3 branch..
--Jani
On Fri, 22 Aug 2003, Sebastian Bergmann wrote:
>Sebastian Bergmann wrote:
>> Using the current CVS of PHP 5's SAPI/CGI on Windows I get the
>> following message for every script
>>
>> No input file specified.
>
> I investigated
I've got an extension which was written for 4.1/4.2, and everything worked
great. I've just (by accident of me not paying attention to an apt-get
dist-upgrade) upgraded to 4.3.2 and I can't get the extension to compile now.
I keep getting bitching about unresolved symbols.
Does anybody have any
Sebastian Bergmann wrote:
> Using the current CVS of PHP 5's SAPI/CGI on Windows I get the
> following message for every script
>
> No input file specified.
I investigated a bit and found out that this broke between August, 4th
and August, 5th, meaning that
cvs upd -D 2003-08-04
work
17 matches
Mail list logo
