I for one, would be very interested in such a module :-)
Dave
> -Original Message-
> From: Bas van Beek [mailto:b...@tobin.nl]
> Sent: Thursday, March 12, 2009 9:26 AM
> To: internals@lists.php.net
> Subject: [PHP-DEV] embed sapi module and multi-threading
>
> Hi,
>
> For a project of mi
I'm having a curious problem with my extension.
I just moved to PHP 5.3-200903031530, made various changes as appropriate
and successfully built it.
Running php -i generates the expected output, including all of the stuff
from my extension.
The odd thing is that PHP always reports:
PHP Warning: P
Hello all.
I am attempting to convert one of my extensions to OOP.
I have a class entry and (I think) I've instantiated an instance of it
within RINIT().
What I haven't been able to do is add a private property to it.
I have the Goleman book and followed the information on pages 148 and 149,
t
On Fri, Feb 13, 2009 at 7:31 PM, David M. Patterson <
dpatter...@dplhenterprises.com> wrote:
> The normal way is to use PHP ini-entries. You can find examples in just
> about every extension out there. Are you sure you need a separate
> configuration file for your extension?
I am writing an extension that requires its own configuration file.
I would prefer to not re-invent the parse a config file wheel and so, have
been trying to use zend_parse_ini_file() function. Unfortunately, I have
been unable to make this work, so far.
If someone would either provide a code sni
Hello all.
I am trying to build PHP 5.3.8 under Windows XP SP3.
I'm using Microsoft Visual Studio V6, SP6 as specified here:
http://wiki.php.net/internals/windows/compiler.
I have installed the Windows Platform SDK V6.1 as specified here:
http://wiki.php.net/internals/windows/windowssdk
Without repeating too much of what has already been said, phpBB3 runs
with its own normalizer (NF[CD]K?) and a full implementation of case
folding along with all sorts of other goodies. For us, it would be best
if semantics were off. Then we could trivially determine whether or not
we should us
Not only are labeled breaks more readable, they are far more maintainable,
especially when nested. With break NUM, you have to change the NUMs
every time you change the nesting. I've shot myself in the foot several
times
that way.
Just my two cents as a long-time PHP user
Dave
Hannes Magnusson sa
