At 9:56 PM +0200 6/21/02, Marcus Börger wrote:
>At 20:29 21.06.2002, Brian France wrote:
>>At 7:23 PM +0200 6/21/02, Marcus Börger wrote:
>>>What i wanted to stree out is that exif uses functions from
>>>mbstring if present.
>>>That means if mbstring is not present it does not use these and
>>>the
At 20:29 21.06.2002, Brian France wrote:
>At 7:23 PM +0200 6/21/02, Marcus Börger wrote:
>>What i wanted to stree out is that exif uses functions from mbstring if
>>present.
>>That means if mbstring is not present it does not use these and the user
>>has to do that stuff for his own.
>>If mbstri
At 7:23 PM +0200 6/21/02, Marcus Börger wrote:
>What i wanted to stree out is that exif uses functions from mbstring
>if present.
>That means if mbstring is not present it does not use these and the
>user has to do that stuff for his own.
>If mbstring is compiled as a shared extension both exif an
At 6:57 PM +0100 6/21/02, Wez Furlong wrote:
> > >If you do decouple mbstring, please make sure that the mbstring headers
> > >are still installed in the pear include directory too!
>
>If mbstring is built as a shared extension, you need to ensure that it's
>headers are also installed in the pea
On Fri, Jun 21, 2002 at 07:23:19PM +0200, Marcus Börger wrote :
> If mbstring is compiled as a shared extension both exif and mbstring will
> work together perfectly but
> exif cannot use mbstring even though it is present and that might/WILL be
> confusing to users.
How feasible is it to
On 21/06/02, "Brian France" <[EMAIL PROTECTED]> wrote:
> My goal is NOT TO REMOVE mbstring FROM THE ext DIRECTORY. Here is
> what I do want:
I understood that.
> I guess my sales pitch of "can be removed from ext" back fired. :-)
> Should of just stuck with "can be built as a shared extensio
At 16:30 21.06.2002, Brian France wrote:
>My goal is NOT TO REMOVE mbstring FROM THE ext DIRECTORY. Here is what I
>do want:
Think we understood that from your first mail!
What i wanted to stree out is that exif uses functions from mbstring if
present.
That means if mbstring is not present it
My goal is NOT TO REMOVE mbstring FROM THE ext DIRECTORY. Here is
what I do want:
I build php for tens of thousands of web servers. Those servers are
all over the world. I only want to build one default PHP core apache
module that only has the standard core things and then everything
else as s
Markus Fischer wrote:
> I'm +1 on removing ext/session too, it's a pretty good idea.
> We can do this along with ext/standard as long as the user
> knows what they're doing ...
I guess what he meant was that there is '--disable-session' to disable
the session extension.
--
Sebastian Bergm
On Fri, Jun 21, 2002 at 08:44:39AM +0900, Yasuo Ohgaki wrote :
> IMO, removing mbstring from PHP is ok as long as user
> knows what they are doing. We can remove other internal
> modules, such as session module also.
I'm +1 on removing ext/session too, it's a pretty good idea.
We can do
At 01:44 21.06.2002, Yasuo Ohgaki wrote:
>Brian France wrote:
>>Ok, what does exif need from mbstring, code wise? Taking a look at it I
>>don't see any references to mbstring in the code.
>
>exif needs mbstring to handle multibyte chars.
Correct ext/exif will work without ext/mbstring but the u
I was just using the ability to remove mbstring from ext as a selling
point to get the patch into PHP. Stays or goes is up to you guys. :-)
What I am doing for work is setting up a bare PHP that can be
installed on all server and then who ever needs mbstring, xml, xslt
or what ever extension c
Brian France wrote:
> Ok, what does exif need from mbstring, code wise? Taking a look at it I
> don't see any references to mbstring in the code.
>
exif needs mbstring to handle multibyte chars.
IMO, removing mbstring from PHP is ok as long as user
knows what they are doing. We can remove oth
Ok, what does exif need from mbstring, code wise? Taking a look at
it I don't see any references to mbstring in the code.
Thanks,
Brian
At 8:27 PM +0200 6/20/02, Marcus Börger wrote:
>You will break ext/exif when removing mbstrings current integration
>
>At 04:17 20.06.2002, you wrote:
>>I am
You will break ext/exif when removing mbstrings current integration
At 04:17 20.06.2002, you wrote:
>I am testing a patch that allows mbstring to be built as a shared
>extension instead of static. This would allow removing any reference to
>mbstring from the core PHP code and making mbstring m
15 matches
Mail list logo
