David Zülke wrote:
Which reminds me I was meaning to ask... Why is ext/xsl not enabled by
default?
Because of its dependency on libxslt.
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
On 8/1/08 6:45 PM, "Arnaud Le Blanc" <[EMAIL PROTECTED]> wrote:
> Hi,
> The ZTS-enabled version of your patch can be found at [1] :)
Thanks Arnaud. I've gone ahead and made the HEAD patch already, wasn't as
bad as I thought it might be. I'll review this hopefully by tomorrow and
then pull into my
Pierre Joye wrote:
ISP, good or bad, enables what we enable. You can see that in the
extension usage statistic (from nexen.net). They have to be taken with
a bit of salt but they represent a good way to see what actually
happens out there. I heard solutions like "educating the ISPs" and
seriously
On Friday 01 August 2008 13:27:44 Lucas Nealan wrote:
> Hi!
>
> On 7/31/08 11:07 PM, "Arnaud Le Blanc" <[EMAIL PROTECTED]> wrote:
>
> > I worked a bit on the ZTS version, this actually fixes many problems with
ZTS
> > on non-windows plateforms :)
> [...snip...]
> > I will send a modified version
On Friday 01 August 2008 5:44:20 am Robert Lemke wrote:
> FWIW: In TYPO3 5.0 we rely on PDO_SQLITE and use it as the default
> database directly after the installation of TYPO3. Not because SQLite
> is such a performant database, but rather because we can use it
> without having to ask the user fo
Hello Internals, Johannes, Lukas,
how about moving ext/dbase to PECL, it is absolutely not a widespread ext
and SQLite stuff has prooven to take over local, single file databases pretty
much.
Given the recent discussion on extensions. From my point of viewe there are
two options:
1) Move every
Hello Stefan,
On 7/30/08, Stefan Esser <[EMAIL PROTECTED]> wrote:
> I am very interested how it performs with YOUR switch statements. And I
> am also very interested if its implementation unexpectedly breaks YOUR
> switch statements.
this is potentially useful for the default parser of PEAR::MDB2
I am not sure about SQLite being "always slow", it works rather well
in some instances. That said, I agree with the general gist of this e-
mail about reviewing closely the extensions that are enabled by
default. That said, most people get their PHP from a distributions,
which typically make
On Fri, 1 Aug 2008, Dmitry Stogov wrote:
> The whole idea is great, but it'll work without problems only if
> switch-tables are constructed at compile (or optimization) time.
>
> The idea also won't work with variables and unresolved constants as
> "case" labels (I saw your extension already carr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> The idea also won't work with variables and unresolved constants as
> "case" labels (I saw your extension already carries about this limitation).
Yeah constants are the reason why I perform the optimization at runtime.
Because the moment a swit
The whole idea is great, but it'll work without problems only if
switch-tables are constructed at compile (or optimization) time.
The idea also won't work with variables and unresolved constants as
"case" labels (I saw your extension already carries about this limitation).
I think the proper way
Hello Robert,
Friday, August 1, 2008, 12:44:20 PM, you wrote:
> Hi folks,
> Am 01.08.2008 um 12:30 schrieb Antony Dovgal:
>> On 01.08.2008 14:20, Scott MacVicar wrote:
>>> ext/pdo_sqlite and ext/sqlite3 use the same underlying lib so its
>>> just another wrapper but without the PDO crap on to
The more extensions enabled by default, the more extensions many developers
can count on being in common builds. Part of PHP's success is the extension
system and the variety of tools it gives the user-base. It is also a nice
peace of mind for library developers to be fairly sure the typical php bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Dmitry,
> As you set the extended_value in shared memory to point into process
> memory the other process will read it and look into it's own memory, and
> of course it won't find proper switch-table there.
In case the opcode cache directly uses o
Hi Stefan,
Opcode caches don't usually copy the op_array.opcodes from shared memory
to process memory, so modification of opcodes may affect other processes
which execute the same op_array.
As you set the extended_value in shared memory to point into process
memory the other process will read it
On 01.08.2008 15:44, Pierre Joye wrote:
It is not about being 100% true or 100% false. We have a couple of
ways to see that, extension usage stastistics and own experiences
(mines in the PEAR time, with htscanner feedbacks on what they use,
and a couple of other things). I provided one source and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dmitry,
while I also believe that the extension should not be included in the
core at the moment I strongly believe that it will be compatible with
every well behaving opcode cache.
Because it modifies op_array during execution...
a) the opcode
Hi,
The proposed patch removes code that implemented shebang line support
(#! /usr/bin/php). Starting with PHP-5.3 it is handled by scanner, and
we don't need to check it twice.
With this check removed, it's become possible to eliminate the open()
syscall (and also several fstat() and mmap() call
On 01.08.2008 14:55, Pierre Joye wrote:
One of the reason of the PHP success is its feature richness.
Since when is "feature richness" == "Sqlite3 must be enabled by default"?
ISP, good or bad, enables what we enable.
Not true.
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime Develo
Please note that the extension modifies op_array and run-time and it
definitely will break opcode caches. However, it is probably possible to
reimplement it on compiler level (may be with new opcode).
Thanks. Dmitry.
Marcus Boerger wrote:
> Hello Stefan,
>
> please discuss with RMs when to mer
Hi!
On 7/31/08 11:07 PM, "Arnaud Le Blanc" <[EMAIL PROTECTED]> wrote:
> I worked a bit on the ZTS version, this actually fixes many problems with ZTS
> on non-windows plateforms :)
[...snip...]
> I will send a modified version of your patch tomorrow.
Sounds great, can't wait to see what you've g
Am 01.08.2008 um 12:11 schrieb Antony Dovgal:
Hello all.
I'd like to express my feelings on the "let's-enable-it-by-default"
mood that has emerged lately.
Extensions enabled by default in 5.2:
8<
-
Total: 22 extensions
Extensions enabled by default in 5.3:
8<
--
Total: 26 exten
On Fri, Aug 1, 2008 at 12:43 PM, Antony Dovgal <[EMAIL PROTECTED]> wrote:
> On 01.08.2008 14:41, Scott MacVicar wrote:
>>>
>>> I know, I know.
>>> But why enable it by default (as well as PDO_SQLITE)? What's so extremely
>>> useful in this extension that every user needs it?
>>
>> The zero configur
Hi folks,
Am 01.08.2008 um 12:30 schrieb Antony Dovgal:
On 01.08.2008 14:20, Scott MacVicar wrote:
ext/pdo_sqlite and ext/sqlite3 use the same underlying lib so its
just another wrapper but without the PDO crap on top.
I know, I know.
But why enable it by default (as well as PDO_SQLITE)? Wh
On 01.08.2008 14:41, Scott MacVicar wrote:
I know, I know.
But why enable it by default (as well as PDO_SQLITE)? What's so
extremely useful in this extension that every user needs it?
The zero configuration aspect, the ability to just throw up a database
in place of your own over complicated
Antony Dovgal wrote:
On 01.08.2008 14:20, Scott MacVicar wrote:
ext/pdo_sqlite and ext/sqlite3 use the same underlying lib so its just
another wrapper but without the PDO crap on top.
I know, I know.
But why enable it by default (as well as PDO_SQLITE)? What's so
extremely useful in this exte
On 01.08.2008 14:20, Scott MacVicar wrote:
ext/pdo_sqlite and ext/sqlite3 use the same underlying lib so its just
another wrapper but without the PDO crap on top.
I know, I know.
But why enable it by default (as well as PDO_SQLITE)?
What's so extremely useful in this extension that every user
Antony Dovgal wrote:
Hello all.
I'd like to express my feelings on the "let's-enable-it-by-default" mood
that has emerged lately.
Extensions enabled by default in 5.2:
ctype
date
dom
filter
hash
iconv
json
libxml
pcre
PDO
pdo_sqlite
posix
Reflection
session
SimpleXML
SPL
SQLite
standard
tok
Hello all.
I'd like to express my feelings on the "let's-enable-it-by-default" mood that
has emerged lately.
Extensions enabled by default in 5.2:
ctype
date
dom
filter
hash
iconv
json
libxml
pcre
PDO
pdo_sqlite
posix
Reflection
session
SimpleXML
SPL
SQLite
standard
tokenizer
xml
xmlreader
xmlw
Hello!
Johannes has packed PHP 5.3.0alpha1 yesterday evening, which you can
find here:
http://downloads.php.net/johannes/
Please test it carefully, and report any bugs in the bug system, but
only if you have a short reproducable test case. The final release is
expected sometime between mi
30 matches
Mail list logo
