Andrei Zmievski schrieb:
> Please send me a new one.
Sorry, maybe I should have just sent the URL :-/
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
PHP Internals - PHP Runtime Developme
<< head explodes from buzzword overload >>
Please send me a new one.
-Andrei
On Apr 19, 2006, at 9:35 PM, Sebastian Bergmann wrote:
Areas of interest include but are not limited to
* Reflection and meta-programming
* Very late binding, dynamic composition, and runtime adaptation
Rasmus Lerdorf wrote:
Has someone been keeping a list of the ideas posted so far? If so,
please give me a URL for that so I can add it to the profile.
Nobody has added things to my wiki, but I can plow through the archive
over the course of the day and make a list available on the wiki.
re
Go to http://code.google.com/soc/mentor_step1.html and sign up if you
are interested in mentoring a student working on a SoC effort.
Has someone been keeping a list of the ideas posted so far? If so,
please give me a URL for that so I can add it to the profile.
Students interested in partici
I just came across this CfP and thought it might be interesting to
our US-based "engine hackers":
Dynamic Languages Symposium 2006 - Technical Papers
Call for papers
Portland, Oregon, United States, October 22, 2006
http://www.dcl.hpi.uni-potsdam.de/dls2006/
The Dynamic Langua
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrei Zmievski wrote:
> The best Derick and I could come up with is a user-specified conversion
> error handler. It would be invoked only when the converter encounters an
> illegal sequence or other serious error. The existing subst, skip, etc
> error
Hi Nuno,
I'm working on a fix (actually I have been for a while but my time has
been limited) and I just commited the fix to ext/unicode/config.w32.
I'll continue working on the other fix tomorrow, unless someone get's
there first.
- Frank
> Hi,
>
> I'm having some troubles building latest HEA
I think that's the right call.
At 01:10 PM 4/19/2006, Ilia Alshanetsky wrote:
5.2 is the next 5.X release that will follow 5.1.3, I don't think we
are in a position to delay 5.1 release any further. My feelings on
the matter are that stability does not seem entirely certain for the
SOAP changes,
Ok, its pretty clear what the problem is. I must not have all 64 bit
libraries on my system. Does this mean that I've gotta find and
recompile ALL of them for PHP to be able to work with them?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/un
Hi,
I'm having some troubles building latest HEAD on windows.
One of the problems is fixed with the patch attatched.
The other is more problematic. I think Visual Studio is having some problems
with macro expansions. Checkout the errors:
ext\standard\file.c(1052) : error C2172: '_to_zstr' : a
On 20.04.2006 02:18, Wez Furlong wrote:
Sounds like those libraries are not 64-bit.
.. and you need to use --with-libdir=lib64
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ok, I may do that. Thanks for the tip.
Brion Vibber wrote:
Jon wrote:
I'm using os X and 64-bit mysql on a G5 and I'm trying to compile
a 64-bit PHP but I seem to be having trouble with the libraries.
[snip]
... then it dies with this stuff in the config.log:
ld64 warning: in /usr/lib/libxm
Jon wrote:
> I'm using os X and 64-bit mysql on a G5 and I'm trying to compile
> a 64-bit PHP but I seem to be having trouble with the libraries.
[snip]
> ... then it dies with this stuff in the config.log:
>
> ld64 warning: in /usr/lib/libxml2.dylib, file does not contain requested
> architecture
Sounds like those libraries are not 64-bit.
--Wez.
On 4/19/06, Jon <[EMAIL PROTECTED]> wrote:
> I'm using os X and 64-bit mysql on a G5 and I'm trying to compile
> a 64-bit PHP but I seem to be having trouble with the libraries.
>
> ld64 warning: in /usr/lib/libxml2.dylib, file does not contain r
Nuno et all.
I agree that the libtidy version we're using is pretty out of date
(2004) so I'm open to upgrading it to the latest *released* version of
tidy (not CVS)[1]. Since you have been keeping up with the library more
then me as of late, I've asked Derick to grant you karma to ext/tidy for
t
I'm using os X and 64-bit mysql on a G5 and I'm trying to compile
a 64-bit PHP but I seem to be having trouble with the libraries.
If I run configure as so:
CFLAGS="-mpowerpc64 -mcpu=G5 -mtune=G5 -arch ppc64"
CPPFLAGS="-mpowerpc64 -mcpu=G5 -mtune=G5 -arch ppc64"
CXXFLAGS="-mpowerpc64 -mcpu=G5
Hmm, no replies. Okay, making executive decision then.. Don't complain
later.
-Andrei
On Apr 18, 2006, at 3:19 PM, Andrei Zmievski wrote:
We had this discussion a long time ago. I don't mind revisiting the
naming conventions, but I want them to be consistent. Consider that
Derick added colla
I've had some time to think about this and Derick and I also kicked
around some ideas in a private conversation.
The situation I am talking about is really about exceptional
circumstances, such as ISO-8859-1 string being treated as a UTF-8 one
or some other condition that results in illegal se
Nuno et all.
I agree that the libtidy version we're using is pretty out of date
(2004) so I'm open to upgrading it to the latest *released* version of
tidy (not CVS)[1]. Since you have been keeping up with the library more
then me as of late, I've asked Derick to grant you karma to ext/tidy for
th
Nuno:
Do you know when the BC break was with libtidy? I'll need to add a
config.m4 check at the very least.
John
On Wed, 2006-04-19 at 23:13 +0200, Steph Fox wrote:
> > I just thought that since we're looking at tidy we might as well update
> > the libs on win32 build boxes :)
>
> Mm but actua
I just thought that since we're looking at tidy we might as well update
the libs on win32 build boxes :)
Mm but actually what's more likely to happen, now that it's turned into a
discussion on upgrading, is precisely nothing. AKA the static build won't be
fixed because 'there's going to be an
5.2 is the next 5.X release that will follow 5.1.3, I don't think we
are in a position to delay 5.1 release any further. My feelings on
the matter are that stability does not seem entirely certain for the
SOAP changes, so I will simply tag the pre-patch version of soap for
RC3 and final 5.1
On Wed, 19 Apr 2006, George Schlossnagle wrote:
> Michael Rasmussen wrote:
>
> >This is a god point.
> >
> >
> No need to inflate Adam's self-image _that_ much.
>
> :)
I think mine just popped. :)
-adam
--
[EMAIL PROTECTED] | http://www.trachtenberg.com
author of o'reilly's "upgrading to php 5
Steph Fox wrote:
It seems very odd to me there can't just be a one-line fix for something
that's broken in 5_1 win32 static build without a whole hoo-ha going down.
The extension doesn't build against the new library without fiddling,
and nor does it build against the library we actually us
Development and testing of the ingres driver pakckage
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi John,
Being older and wiser than I was this morning:
tidySetInCharEncoding
tidySetOutCharEncoding
tidyOptGetDoc
tidyOptGetDocLinksList
tidyOptGetNextDocLinks
tidyAttrGetById
are the only newly introduced functions between the two library versions.
The _only_ problem with the current static
There _isn't_ a PECL tidy version 2.0...!
Steph Fox wrote:
Something's odd in the manual then:
Note: Tidy 1.0 is just for PHP 4.3.x, while Tidy 2.0 is just for PHP 5.
Which refers to ext/tidy version (AFAICT).
exactly. The PECL tidy extension version 2.0 doesn't work with PHP 4
because i
It seems very odd to me there can't just be a one-line fix for something
that's broken in 5_1 win32 static build without a whole hoo-ha going down.
The extension doesn't build against the new library without fiddling, and
nor does it build against the library we actually use. The difference
Steph Fox wrote:
Something's odd in the manual then:
Note: Tidy 1.0 is just for PHP 4.3.x, while Tidy 2.0 is just for PHP 5.
Which refers to ext/tidy version (AFAICT).
exactly. The PECL tidy extension version 2.0 doesn't work with PHP 4 because
it uses some zend engine 2 specific stuff (OO
Michael Rasmussen wrote:
On Wed, 19 Apr 2006 13:52:13 -0400, Adam Maccabee Trachtenberg wrote:
Not if you think the improvements will break the code base because you
don't have time to do sufficient testing. I would prefer to avoid
regressions in minor releases and would like to use the lon
On Wed, 2006-04-19 at 14:27 +0200, Steph Fox wrote:
> Really this is down to John Coggeshall (as maintainer) - unless someone else
> feels like going and finding a newer version of libtidy and testing it with
> the existing extension(s) - e.g. would a newer version also bring other new
> functio
On Wed, 19 Apr 2006 13:52:13 -0400, Adam Maccabee Trachtenberg wrote:
>
> Not if you think the improvements will break the code base because you
> don't have time to do sufficient testing. I would prefer to avoid
> regressions in minor releases and would like to use the longer 5.2
> beta period f
On Wed, 19 Apr 2006, Michael Rasmussen wrote:
> Maybe I have missed something lately. It think your argumentation is
> twisted, is it not normally the other way round? You increase major
> when new functionality is added and only change minor when bugs
> and/or improvements to current code base is
On Wed, 19 Apr 2006 12:57:17 -0400, Adam Maccabee Trachtenberg wrote:
>
> I would prefer not to break ext/soap, so I suggest 5.2.0. My main
> reason for delaying is that this does not add any new functionality:
> it's "only" performance improvements. People who really need it can
> run latest CVS
Steph Fox wrote:
Something's odd in the manual then:
Note: Tidy 1.0 is just for PHP 4.3.x, while Tidy 2.0 is just for PHP 5.
Which refers to ext/tidy version (AFAICT).
Regards,
--
Michael - http://dev.iworks.at/ext-http/http-functions.html.gz
--
PHP Internals - PHP Runtime Development Mail
On Wed, 19 Apr 2006, Dmitry Stogov wrote:
> Now you can enable disk and/or memory cache through configuration directive
> "soap.wsdl_cache" in php.ini.
> It can have one of the following values WSDL_CACHE_NONE, WSDL_CACHE_DISK,
> WSDL_CACHE_MEMORY, WSDL_CACHE_BOTH. The default value is WSDL_CACHE_
Nuno, will this also work for 4_3 branch?
Yep, the libtidy API hasn't changed.
Something's odd in the manual then:
Note: Tidy 1.0 is just for PHP 4.3.x, while Tidy 2.0 is just for PHP 5.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub
Ah Sorry. I haven't compiled PHP on windows for some time now.
Attached is a patch thats fixes the problem.
Nuno
Latest CVS (SF anon CVS worked for me) doesn't compile with error:
ext\tidy\tidy.c(586) : error C2152: 'function' : pointers to functions
with different attributes
Edin
Nuno Lop
I mean ext/tidy from 5.1 doesn't compile with this latest version of
libtidy. Libtidy itself compiles fine on windows.
Edin
Edin Kadribasic wrote:
> Latest CVS (SF anon CVS worked for me) doesn't compile with error:
>
> ext\tidy\tidy.c(586) : error C2152: 'function' : pointers to functions
> wit
Latest CVS (SF anon CVS worked for me) doesn't compile with error:
ext\tidy\tidy.c(586) : error C2152: 'function' : pointers to functions
with different attributes
Edin
Nuno Lopes wrote:
> answering both e-mails:
>
>> Nuno, which version of libtidy do you think we should use for bundiling
>> w
answering both e-mails:
Nuno, which version of libtidy do you think we should use for bundiling
with the windows distribution?
latest CVS. It is stable ATM (but checkout with a developer account, because
sourceforge's anonymous cvs servers are currently broken).
Nuno, will this also work f
Hi,
I made a cleanup of Andrei's patch for caching WSDL in memory.
Now you can enable disk and/or memory cache through configuration directive
"soap.wsdl_cache" in php.ini.
It can have one of the following values WSDL_CACHE_NONE, WSDL_CACHE_DISK,
WSDL_CACHE_MEMORY, WSDL_CACHE_BOTH. The default va
> Seems like AST is a great tool for code analysis, development,
> debugging, re-factoring, optimizing -- but I don't see how that makes
> it a winner for the run-time compilation.
Remember though, that with PHP6 it's planned to include a bytecodecache with
the standard distribution (right?), so
Nuno, will this also work for 4_3 branch?
>I updated my copy from Edin's collection last week. It's newer than
>last year's, but I'm struggling to find any form of 'version' in there
>to know exactly what I have in front of me. So what are you talking
>about? Update from what, to what, and for
Nuno, which version of libtidy do you think we should use for bundiling
with the windows distribution?
Edin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
>I updated my copy from Edin's collection last week. It's newer than last
>year's, but I'm struggling to find any form of 'version' in there to
>know exactly what I have in front of me. So what are you talking about?
>Update from what, to what, and for which PHP build?
I'm talking about the li
>I updated my copy from Edin's collection last week. It's newer than last
>year's, but I'm struggling to find any form of 'version' in there to know
>exactly what I have in front of me. So what are you talking about? Update
>from what, to what, and for which PHP build?
I'm talking about the li
I updated my copy from Edin's collection last week. It's newer than last
year's, but I'm struggling to find any form of 'version' in there to know
exactly what I have in front of me. So what are you talking about? Update
from what, to what, and for which PHP build?
I'm talking about the libtid
I updated my copy from Edin's collection last week. It's newer than last
year's, but I'm struggling to find any form of 'version' in there to know
exactly what I have in front of me. So what are you talking about? Update
from what, to what, and for which PHP build?
BTW, the libtidy could be u
OK. I've just found that that .defs file is _only_ used by the static win32
build. It doesn't affect anything else, on any other platform.
That makes fixing it even easier :) one line instead of three, you just
don't export the function that doesn't exist. If/when we ever get that
function in
BTW, the libtidy could be updated :) It had a major optimization a few time
ago (it decreased my bechmark running time by ~30%).
Nuno
- Original Message -
From: "Steph Fox" <[EMAIL PROTECTED]>
To: "internals"
Cc: "Edin" <[EMAIL PROTECTED]>
Sent: Wednesday, April 19, 2006 12:00 PM
Sub
Oops, forget it. The problem with having both PECL and src on board is I
assumed I was building against the one with this change in it. I wasn't - I
was building against the one that didn't have tidyOptGetDoc in the export
list AT ALL.
Just ran a test and found this is illegal syntax :( so bac
This allows static builds under win32 despite the fact that tidyOptGetDoc()
doesn't exist in the libtidy.lib we're linking against.
It needs applying to php_tidy.def everywhere libtidy v 2 is used - that is,
ext/tidy in CVS HEAD and PHP_5_1, and CVS HEAD pecl/tidy.
In all three cases there is
53 matches
Mail list logo
