Hello Markus,
Sunday, November 30, 2003, 10:59:50 PM, you wrote:
> Hi,
> On Sat, Nov 29, 2003 at 06:09:36PM +0100, Marcus Boerger wrote :
>> this works now.
> Thanks. Sorry for the order of reply of the mails, my spam filer
> catches this one and I only discovered it yet.
>> >
Hello Marcus,
Sunday, November 30, 2003, 1:35:23 PM, you wrote:
> Hello Wez,
> Sunday, November 30, 2003, 11:01:51 AM, you wrote:
>> There is no point moving unmaintained code from ext to pecl;
>> its just a waste of time until we can solve the problem at
>> packaging time, which is why I'm sug
We've defined a custom libxml2 error handler,
php_libxml_error_handler(), that makes error messages go through
php_error() instead of printing to stderr.
Unfortunately, libxml2 doesn't make one call to the error function for
each error. Sometimes it seems to do it once per
character. Unfortunately
The php_dom_ctx_error_level() function in DOM document.c assumes that
input->filename is always non-null. This is not true when the file is
an entity.
You can trigger this by killing your Internet connection and then
loading any XML file that references an external entity. For example:
http://www
hi adam
it's commited.
thanks fot the patch
chregu
On 12/1/03 9:10 AM, Adam Maccabee Trachtenberg wrote:
The php_dom_ctx_error_level() function in DOM document.c assumes that
input->filename is always non-null. This is not true when the file is
an entity.
You can trigger this by killing your In
> From: Andi Gutmans [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 30, 2003 12:10 AM
> The strict was introduced so that we can add warnings about practices we
> recommend and deprecated behavior.
> I think "var" belongs there.
> We could remove E_STRICT from E_ALL (although that'd be a bit
At 07:49 AM 12/1/2003 +0100, Marcus Boerger wrote:
Hello Andrei,
Friday, November 28, 2003, 1:59:35 PM, you wrote:
> On Thu, 27 Nov 2003, Marcus Boerger wrote:
>> hellyThu Nov 27 14:24:38 2003 EDT
>>
>> Modified files:
>> /ZendEngine2 zend_API.c
>> Log:
>> Convert ob
At 12:50 AM 12/1/2003 -0500, Adam Maccabee Trachtenberg wrote:
On Sun, 30 Nov 2003, Andi Gutmans wrote:
> At 11:59 AM 11/28/2003 -0500, Adam Maccabee Trachtenberg wrote:
> >As far as I'm concerned, if you don't want your object to be
> >auomatically cast to a string, you shouldn't provide a __toS
At 12:54 AM 12/1/2003 -0500, Adam Maccabee Trachtenberg wrote:
On Sun, 30 Nov 2003, Andi Gutmans wrote:
> I kind of agree with Andrei here. We discussed in the past that
> __toString() will not propogate to every place in the engine where we check
> for IS_STRING but will only effect print.
> I th
At 07:54 AM 12/1/2003 +0100, Marcus Boerger wrote:
Hello Andi,
Sunday, November 30, 2003, 12:08:33 AM, you wrote:
> At 11:59 AM 11/28/2003 -0500, Adam Maccabee Trachtenberg wrote:
>>On Fri, 28 Nov 2003, Andrei Zmievski wrote:
>>
>> > On Thu, 27 Nov 2003, Marcus Boerger wrote:
>> > > Convert obj
>>And if at all we drop the auto-conversion then what we get is:
>>print toupper((string)$obj);
>>Wow, no more elegant php - no more typeless php.
PHP was never "elegant" in this meaning - you never could do
toupper($object) and expect something meaningful. I also don't see any
elegancy in it -
On Mon, 1 Dec 2003, Stanislav Malyshev wrote:
>>>And if at all we drop the auto-conversion then what we get is:
>>>print toupper((string)$obj);
>>>Wow, no more elegant php - no more typeless php.
>
>PHP was never "elegant" in this meaning - you never could do
>toupper($object) and expect somethin
It *needs* to work so that overloaded objects (simplexml, COM etc.)
can have their cast handlers called.
Andi wrote:
> No. You would get print toupper($obj->__toString()).
> I am not sure (string) cast on objects should work.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
On Mon, 1 Dec 2003, Wez Furlong wrote:
> It *needs* to work so that overloaded objects (simplexml, COM etc.)
> can have their cast handlers called.
Yeah, it's pretty much needed for those extensions... though I don't
like these things for normal user defined objects... atleast extensions
should h
There is no __toString in overloaded objects; thats the reason that the
(string) cast should work on objects.
> > It *needs* to work so that overloaded objects (simplexml, COM etc.)
> > can have their cast handlers called.
>
> Yeah, it's pretty much needed for those extensions... though I don't
>
On Mon, 1 Dec 2003, Wez Furlong wrote:
> There is no __toString in overloaded objects; thats the reason that the
> (string) cast should work on objects.
Ah, of course :)
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
I don't think casting an object to a string should work.
I don't see why this is any better than the more verbose $obj->__toString().
Can you please explain in what situation you need __toString() to be called
for SimpleXML and COM automatically and we can try and think of a solution
together. A
I'm talking about (string)$obj calling the cast handler in overloaded
objects; COM does not have a __toString() method, and we shouldn't
be cluttering up the "method-space" for overloaded objects - what
if the underlying object has a __toString() method?
I'm not particularly worried about __toStri
WF>> I'm talking about (string)$obj calling the cast handler in overloaded
WF>> objects; COM does not have a __toString() method, and we shouldn't
WF>> be cluttering up the "method-space" for overloaded objects - what
WF>> if the underlying object has a __toString() method?
If it does, it would be
serialize($obj) is different from serialize((string)$obj);
The reason I mentioned this is that serialize($obj) is currently
meaningless for COM objects, so people are using
serialize((string)$obj) to get a string representation.
--Wez.
> Just a moment here. You imply that serialize() would use
WF>> The reason I mentioned this is that serialize($obj) is currently
WF>> meaningless for COM objects, so people are using
WF>> serialize((string)$obj) to get a string representation.
I don't understand - what is the meaning of serialize((string)$obj)? What
should it return?
--
Stanislav Malys
> WF>> The reason I mentioned this is that serialize($obj) is currently
> WF>> meaningless for COM objects, so people are using
> WF>> serialize((string)$obj) to get a string representation.
>
> I don't understand - what is the meaning of serialize((string)$obj)? What
> should it return?
Just pret
WF>> What I'm trying to say is that (string)$obj really should work (as it
WF>> does currently) for overloaded objects because they might not have a
I see where you are heading. I would say it should work for objects with
explicit cast, but not implicitly, then. Meaning, the cast opcode should
c
I would like to propose that tidy extension be bundled with PHP 5.
First of all it'll provide an easy means to validate and/or fix HTML input for
webforms, which can also help existing functions such as strip_tags(). The
extension can also be used to reduce HTML output by removing formatting,
On Monday, Dec 1, 2003, at 14:45 Europe/Copenhagen, Ilia Alshanetsky
wrote:
I would like to propose that tidy extension be bundled with PHP 5.
First of all it'll provide an easy means to validate and/or fix HTML
input for
webforms, which can also help existing functions such as strip_tags().
T
On 2003/12/01, at 19:39, Andi Gutmans wrote:
At 12:50 AM 12/1/2003 -0500, Adam Maccabee Trachtenberg wrote:
On Sun, 30 Nov 2003, Andi Gutmans wrote:
> At 11:59 AM 11/28/2003 -0500, Adam Maccabee Trachtenberg wrote:
> >As far as I'm concerned, if you don't want your object to be
> >auomatically c
At 01:21 PM 12/1/2003 +, Wez Furlong wrote:
> WF>> The reason I mentioned this is that serialize($obj) is currently
> WF>> meaningless for COM objects, so people are using
> WF>> serialize((string)$obj) to get a string representation.
>
> I don't understand - what is the meaning of serialize((s
Hi, all
Current HEAD eats all memory and dies, trying to execute any script (,
for example).
Version of HEAD from 2003-11-29 and current PHP_4_3 (both are built some minutes ago)
work fine on the same machine.
My configuration:
Linux 2.4.21
autoconf 2.57
automake 1.7
libtool 1.5
gcc 3.3
glibc
I favour a), if you mean that (string)$com_object will work.
I'm not so bothered with userspace objects.
b) is just wrong for overloaded objects; if we do some magic
and either hide an existing __toString() method, or call one
with the wrong parameters (it might implement one differently
to the wa
+1 from me; very useful for screen scraping as well as validation and
fixing.
--Wez.
- Original Message -
From: "Ilia Alshanetsky" <[EMAIL PROTECTED]>
To: "PHP Internals" <[EMAIL PROTECTED]>
Sent: Monday, December 01, 2003 1:45 PM
Subject: [PHP-DEV] Tidy & PHP5
> I would like to propos
> Current HEAD eats all memory and dies, trying to execute any script (, for example).
> Version of HEAD from 2003-11-29 and current PHP_4_3 (both are built some
minutes ago) work fine on the same machine.
>
Thank god ;-) i thought it was on my machine only!
Gr,
JOhn
--
PHP Internals - PHP Run
On Mon, 1 Dec 2003 15:51:54 +0100
"John Huntjens" <[EMAIL PROTECTED]> wrote:
> > Current HEAD eats all memory and dies, trying to execute any script ( phpinfo(); ?>, for example).
> > Version of HEAD from 2003-11-29 and current PHP_4_3 (both are built some
> minutes ago) work fine on the same mach
Its a binary maths problem:
#define E_ALL (E_ERROR | E_WARNING | E_PARSE | E_NOTICE | E_CORE_ERROR |
E_CORE_WARNING | E_COMPILE_ERROR | E_COMPILE_WARNING | E_USER_ERROR |
E_USER_WARNING | E_USER_NOTICE)
I guess either slotting E_STRICT in the and defining E_ALL_PHP5 or
(E_ALL_PHP4 and redefini
+1 if this is counted :)
Moriyoshi
On 2003/12/01, at 22:45, Ilia Alshanetsky wrote:
I would like to propose that tidy extension be bundled with PHP 5.
First of all it'll provide an easy means to validate and/or fix HTML
input for
webforms, which can also help existing functions such as strip_t
> I would like to propose that tidy extension be bundled with PHP 5.
Uhh... +1 from me, too. :)
John
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
+1 there are ... a lot :-)
- Original Message -
From: "John Coggeshall" <[EMAIL PROTECTED]>
To: "PHP Internals" <[EMAIL PROTECTED]>
Sent: Monday, December 01, 2003 4:31 PM
Subject: Re: [PHP-DEV] Tidy & PHP5
> > I would like to propose that tidy extension be bundled with PHP 5.
>
> Uhh..
Works fine for me.
--Jani
On Mon, 1 Dec 2003, Antony Dovgal wrote:
>Hi, all
>
>Current HEAD eats all memory and dies, trying to execute any script (phpinfo(); ?>, for example). Version of HEAD from 2003-11-29 and current
>PHP_4_3 (both are built some minutes ago) work fine on t
All I want to be able to do is this:
$s = simplexml_load_file('rss.xml');
foreach ($s->item as $item) {
print htmlentities($item->title . "\n");
}
That's not *all* I want to do, but this is my three-line test case. If
we can figure out a way to make this work, then I'm a happy camper.
I *don
> > > Current HEAD eats all memory and dies, trying to execute any script
( > phpinfo(); ?>, for example).
> > > Version of HEAD from 2003-11-29 and current PHP_4_3 (both are built
some
> > minutes ago) work fine on the same machine.
> > >
> >
> > Thank god ;-) i thought it was on my machine only!
AMT>> I *don't* think it's realisitic to make a person explictly cast
AMT>> $item->title to a string here. That's not SimpleXML, that's
If it's not a string - definitely it does.
AMT>> ConfusingXML, particularly when this works perfectly fine:
If you find it confusing - change API of SimpleXML s
Jani Taskinen wrote:
> Works fine for me.
Works fine here, too. (Win32)
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Das Buch zu PHP 5: http://professionelle-softwareentwicklung-mit-php5.de/
--
PHP Internals - PHP Runtime Development Mailin
On Mon, 1 Dec 2003, Stanislav Malyshev wrote:
> AMT>> I *don't* think it's realisitic to make a person explictly cast
> AMT>> $item->title to a string here. That's not SimpleXML, that's
>
> If it's not a string - definitely it does.
>
> AMT>> ConfusingXML, particularly when this works perfectly fi
On Mon, 1 Dec 2003 17:40:09 +0200 (EET)
Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
> Works fine for me.
>
I've already re-checked that about 10 times.
2 minutes ago I've repeated all the process from the very beginning:
#cvs co php-src
#./buildconf
#./configure ...blah-blah (configure
On Mon, 1 Dec 2003, John Huntjens wrote:
> > > > Current HEAD eats all memory and dies, trying to execute any script
> ( > > phpinfo(); ?>, for example).
> > > > Version of HEAD from 2003-11-29 and current PHP_4_3 (both are built
> some
> > > minutes ago) work fine on the same machine.
> > > >
> >
Try with the snapshot from http://snaps.php.net
--Jani
On Mon, 1 Dec 2003, Antony Dovgal wrote:
>On Mon, 1 Dec 2003 17:40:09 +0200 (EET)
>Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
>>
>> Works fine for me.
>>
>
>I've already re-checked that about 10 times.
>
>2 minute
DR>> To make it simple to use? I agree with Adam here, with the new
It may make one particular case of use simple. It would make understanding
even this case complicated, and will complicate a lot of other cases of
which we didn't think now.
DR>> overloaded objects you can finally do nice thing
> > What i more worried about:
> > Is'nt there a quality check about things commited to cvs?
> > It shoud not be possible to break things in such a fundamental way!!
>
> Oh shutup. It works just fine. You guys must be doing something wrong.
No I won't!
I compile a snap every day, in the same co
On Mon, 1 Dec 2003 17:03:43 +0100 (CET)
Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Mon, 1 Dec 2003, John Huntjens wrote:
>
> > > > > Current HEAD eats all memory and dies, trying to execute any script
> > ( > > > phpinfo(); ?>, for example).
> > > > > Version of HEAD from 2003-11-29 and curre
On Mon, 1 Dec 2003 17:12:02 +0100
"John Huntjens" <[EMAIL PROTECTED]> wrote:
>
>
> > > What i more worried about:
> > > Is'nt there a quality check about things commited to cvs?
> > > It shoud not be possible to break things in such a fundamental way!!
> >
> > Oh shutup. It works just fine. You
On Monday, Dec 1, 2003, at 17:12 Europe/Copenhagen, John Huntjens wrote:
What i more worried about:
Is'nt there a quality check about things commited to cvs?
It shoud not be possible to break things in such a fundamental way!!
Oh shutup. It works just fine. You guys must be doing something wrong
> >
> >
> >>> What i more worried about:
> >>> Is'nt there a quality check about things commited to cvs?
> >>> It shoud not be possible to break things in such a fundamental way!!
> >>
> >> Oh shutup. It works just fine. You guys must be doing something wrong.
> >
> > No I won't!
>
>
> Hey John,
John instead of making a nuisance of yourself, why not find the problem that
affects your installation (that 3 developers cannot replicate) and suggest a
fix?
Ilia
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Maintaining Czech documentation. If I will find mistake in English documentation, I
can send a patch to someone else.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, 1 Dec 2003 18:04:46 +0200 (EET)
Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
> Try with the snapshot from http://snaps.php.net
no, php5-200312011430 didn't help (just ./configure; make).
I've tried this snapshot and current CVS-version on 2 linux-boxes with the same result.
It still tr
Jakub Vrana wrote:
Maintaining Czech documentation. If I will find mistake in English documentation, I can send a patch to someone else.
Jakub has already helped with the english documentation :
http://news.php.net/article.php?group=php.doc&article=969357093
http://news.php.net/article.php?grou
On Mon, 1 Dec 2003, Stanislav Malyshev wrote:
> DR>> To make it simple to use? I agree with Adam here, with the new
>
> It may make one particular case of use simple. It would make understanding
> even this case complicated, and will complicate a lot of other cases of
> which we didn't think now.
> no, php5-200312011430 didn't help (just ./configure; make).
> I've tried this snapshot and current CVS-version on 2 linux-boxes with the
same result.
> It still tries to eat memory =(
>
> Second machine is:
> Linux 2.4.18-5
> gcc-2.96
> autoconf 2.50
> automake 1.4-p5
> libtool 1.5
> Apache 1.3.2
Hello Moriyoshi,
Monday, December 1, 2003, 2:56:29 PM, you wrote:
> On 2003/12/01, at 19:39, Andi Gutmans wrote:
>> At 12:50 AM 12/1/2003 -0500, Adam Maccabee Trachtenberg wrote:
>>> On Sun, 30 Nov 2003, Andi Gutmans wrote:
>>>
>>> > At 11:59 AM 11/28/2003 -0500, Adam Maccabee Trachtenberg wrot
What's the chance of having a __toString() in an external object model
(note the two underscores :)
Andi
At 02:26 PM 12/1/2003 +, Wez Furlong wrote:
I favour a), if you mean that (string)$com_object will work.
I'm not so bothered with userspace objects.
b) is just wrong for overloaded object
AMT>> Are we discussing this feature's technical or aesthetic merits? Or
AMT>> both?
Technical.
AMT>> foreach ($dom->getElementsByTagname('person') as $person) {
AMT>> list($firstname) = $person->getElementsByTagname('firstname');
AMT>> $firstname_text_value = $firstname->firstChi
Hello Stanislav,
Monday, December 1, 2003, 5:05:14 PM, you wrote:
DR>>> To make it simple to use? I agree with Adam here, with the new
> It may make one particular case of use simple. It would make understanding
> even this case complicated, and will complicate a lot of other cases of
> which w
MB>> If you don't understand XML then it is harder to understand. If you
Well, let's suppose I do understand XML for some measure.
MB>> you are now basically forced to do fucking code like DOM - thanks -
MB>> no more simple.
Making particular case of XML handling simple is good if it doesn't mak
Hey,
I don't quite understand why SimpleXML can't return a string. Why does it
need to return an object? It should know how to differentiate between
read/write mode, and return a string in read mode and a proxy object in
write mode.
What am I missing?
I agree that we should allow for SimpleXML'
It's probably a lot higher than you think, given that other
object models are likely to use a similar naming convention :-)
I still think it is a bad idea to hide methods like this for
overloaded objects; we have the cast handler and (to my eyes)
$foo = (string)$obj;
looks simpler and less magic
It can be resolved at compile-time.
My main problem is not with the casting operator but with auto-casting all
throughout the engine including parameter passing. I have a very bad
feeling that stuff will break such as array offset assigning.
Andi
At 04:58 PM 12/1/2003 +, Wez Furlong wrote:
> Now trying on a second machine:
> Linux 2.4.18
> gcc-3.3
> autoconf 2.57
> automake 1.7
> libtool 1.5
> Apache 2.0.48
On this machine build is OK
JOhn
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Current HEAD built as Debug_TS on Windows 2000:
http://wopr/index.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
Fatal error: Possible integer overflow in memory allocation
(2 * -858993460 + 1) in Unknown on line 0
--
Sebastian Bergmann
http://sebastian-bergmann.de/ ht
> I would like to propose that tidy extension be bundled with PHP 5.
+1
Georg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Mon, 1 Dec 2003, Andi Gutmans wrote:
> I don't quite understand why SimpleXML can't return a string. Why does it
> need to return an object? It should know how to differentiate between
> read/write mode, and return a string in read mode and a proxy object in
> write mode.
That may be a solutio
On Dec 1, 2003, at 11:52 AM, Marcus Boerger wrote:
Hello Stanislav,
Monday, December 1, 2003, 5:05:14 PM, you wrote:
DR>>> To make it simple to use? I agree with Adam here, with the new
It may make one particular case of use simple. It would make
understanding
even this case complicated, and w
before bundling i'd like to see the api refined...
right now it's not possible to work with more than one html-doc at a
time. (tidy_parse_file() does not return a resource to the internal
tidy doc, so you can only have one doc at a time)
also we should ask ourself if (i haven't used tidy so i m
AMT>> $s = simplexml_load_file('file.xml');
AMT>> $s->person->xsearch('/my/xpath/query');
This makes fetch for read.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.109
--
PHP Internals - PHP Runtime Development Mailing List
To unsub
Hey,
Let's try and summarize this discussion and try and see what solution we
can come up with.
The change which was made in convert_to_string() is quite problematic. It
touches a very fundamental engine function and changes the behavior of tons
of places. For example:
a) include $obj; will not
On Mon, 1 Dec 2003, Stanislav Malyshev wrote:
> AMT>> $s = simplexml_load_file('file.xml');
> AMT>> $s->person->xsearch('/my/xpath/query');
>
> This makes fetch for read.
I'm with Andi and George. We should just fix SimpleXML to return
strings instead of objects when there are no descendant nodes
On Dec 1, 2003, at 12:51 PM, Adam Maccabee Trachtenberg wrote:
On Mon, 1 Dec 2003, Stanislav Malyshev wrote:
AMT>> $s = simplexml_load_file('file.xml');
AMT>> $s->person->xsearch('/my/xpath/query');
This makes fetch for read.
I'm with Andi and George. We should just fix SimpleXML to return
string
On Mon, 1 Dec 2003 18:21:33 +0100
"John Huntjens" <[EMAIL PROTECTED]> wrote:
> > Now trying on a second machine:
> > Linux 2.4.18
> > gcc-3.3
> > autoconf 2.57
> > automake 1.7
> > libtool 1.5
> > Apache 2.0.48
>
> On this machine build is OK
I've changed autoconf to 2.57 and automake to 1.7 - a
On Mon, 1 Dec 2003, George Schlossnagle wrote:
> [puts on evil twin hat]
Theo?
> To play devil's advocate to the idea - the problem with it is that it
> requires a bunch of extra code when examining an unknown document.
> This is similar to the (promised by Sterling to be fixed) quirk of
> Simpl
Hi,
As an observer of this whole debate, I'd like to point out that if
__toString() will be magical anywhere, it must be magical everywhere PHP
would normally do an implicit cast, otherwise it does nothing but
confuse the issue. implicit cast to string always happens when using
string operato
In the primary use of tidy (which is to validate HTML), there is very
little need for a returned resource other than to clutter the namespace.
Unlike most extensions, where it would be useful imo the resource is
unnecessary. Since we can reuse the container for the tidy
documentation, it's much fas
On Mon, 1 Dec 2003, Antony Dovgal wrote:
>On Mon, 1 Dec 2003 18:04:46 +0200 (EET)
>Jani Taskinen <[EMAIL PROTECTED]> wrote:
>
>>
>> Try with the snapshot from http://snaps.php.net
>
>no, php5-200312011430 didn't help (just ./configure; make).
>I've tried this snapshot and current CVS-version
Jani Taskinen wrote:
> Was there some script to go with this..?
Maybe this is related to the problem with PHP's logos I posted earlier?
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Das Buch zu PHP 5: http://professionelle-softwareentwicklung-
I'm not really sure on what's the best way to handle the string
conversion problem, as I haven't worked with SimpleXML yet. Andi's
examples on the other hand aren't convincing enough for me so here my
comments:
Andi Gutmans wrote:
a) include $obj; will not error out but convert the object to a
On Mon, 1 Dec 2003, Antony Dovgal wrote:
>BTW, I've already asked about this message:
>
>buildconf: autoconf version 2.50 (ok)
>buildconf: Your version of autoconf likely contains buggy cache code.
> Running cvsclean for you.
> To avoid this, install autoconf-2.13 and autom
Finally..if you had mentioned THIS in the first place, you wouldn't
have wasted our time..
(didn't I ask for some reproducing procedure? I don't remember anymore :)
--Jani
On Mon, 1 Dec 2003, Antony Dovgal wrote:
>On Mon, 1 Dec 2003 18:21:33 +0100
>"John Huntjens" <[EMA
On Mon, 1 Dec 2003, Sebastian Bergmann wrote:
>Jani Taskinen wrote:
>> Was there some script to go with this..?
>
> Maybe this is related to the problem with PHP's logos I posted earlier?
Eh? What logos? (either I'm getting senile or I'm not getting some mails)
--Jani
--
PHP
This does not fix the problem.
mssql_query is designed to stop fetching for each result. Use
mssql_next_result() to move the internal pointer to the nex result and
process the data.
I have tested the code provided with the bug report and it works as I
expect (no crash).
- Frank
> I believe the
Jani Taskinen wrote:
> Eh? What logos?
Current HEAD built as Debug_TS on Windows 2000:
http://wopr/index.php?=PHPE9568F34-D428-11d2-A769-00AA001ACF42
Fatal error: Possible integer overflow in memory allocation
(2 * -858993460 + 1) in Unknown on line 0
--
Sebastian Bergmann
http:/
On Mon, 1 Dec 2003, Antony Dovgal wrote:
> On Mon, 1 Dec 2003 18:21:33 +0100
> "John Huntjens" <[EMAIL PROTECTED]> wrote:
>
> > > Now trying on a second machine:
> > > Linux 2.4.18
> > > gcc-3.3
> > > autoconf 2.57
> > > automake 1.7
> > > libtool 1.5
> > > Apache 2.0.48
> >
> > On this machine bu
Derick, looking at the code it looks like we are checking for the a= case
and handling that correctly, but not the =a case. As in foo.com?a= vs
foo.com?=a
Not sure if it is yours or my bug. Currently in India and the connection
here is too damn slow to browse through cvs.
-Rasmus
On Mon, 1 De
On Mon, 1 Dec 2003, Rasmus Lerdorf wrote:
> Derick, looking at the code it looks like we are checking for the a= case
> and handling that correctly, but not the =a case. As in foo.com?a= vs
> foo.com?=a
That is something I did not touch, but I found the problem which caused
this...forgot to chan
On Sun, Nov 30, 2003 at 01:10:25AM +0200, Andi Gutmans wrote:
> The strict was introduced so that we can add warnings about practices we
> recommend and deprecated behavior.
> I think "var" belongs there.
> We could remove E_STRICT from E_ALL (although that'd be a bit hacky) and
> save ppl the tr
On Mon, 1 Dec 2003, Derick Rethans wrote:
> On Mon, 1 Dec 2003, Rasmus Lerdorf wrote:
>
> > Derick, looking at the code it looks like we are checking for the a= case
> > and handling that correctly, but not the =a case. As in foo.com?a= vs
> > foo.com?=a
>
> That is something I did not touch, b
IMHO, think that __toString should be explicitly
called as in java. Sure it would be great if it works
when using print, echo, etc, mean that cases when its
obvious that should evaluate to string. But ALL other
cases should be evaluated only explicitly. Maybe using
a diferent syntax for that as (st
At 02:37 PM 12/1/2003 -0500, Daniel Convissor wrote:
On Sun, Nov 30, 2003 at 01:10:25AM +0200, Andi Gutmans wrote:
> The strict was introduced so that we can add warnings about practices we
> recommend and deprecated behavior.
> I think "var" belongs there.
> We could remove E_STRICT from E_ALL (al
Does this mean I can enable my GetLongPathName() patch in
tsrm_virtual_cwd.c (I think it also requires Win98 but I kept it out
because there are people who are still using Windows 95). I think we
decided that we will continue supporting Windows 95 and I #If 0'd my patch.
Also, I just saw (and fi
On Mon, Dec 01, 2003 at 10:15:46PM +0200, Andi Gutmans wrote:
>
> I don't quite understand the problem. E_STRICT was only meant for people
> who really want to be pedantic. I think we can make it not part of E_ALL.
> Is that OK?
Better. The only drawback is people who do want to be pedantic wi
At 03:32 PM 12/1/2003 -0500, Daniel Convissor wrote:
On Mon, Dec 01, 2003 at 10:15:46PM +0200, Andi Gutmans wrote:
>
> I don't quite understand the problem. E_STRICT was only meant for people
> who really want to be pedantic. I think we can make it not part of E_ALL.
> Is that OK?
Better. The only
> before bundling i'd like to see the api refined...
>
> right now it's not possible to work with more than one html-doc at a
> time. (tidy_parse_file() does not return a resource to the internal
> tidy doc, so you can only have one doc at a time)
Yes, Thies is right here! But
s/resource/object
I'm not sure if we should whole-heartedly abandon win95; I'd love to,
I'm just not sure. CGI/FastCGI sapi will only run under NT and later
(because of the named pipe stuff). For the people running PHP in a
web server, this shouldn't be a problem (who would be mad enough to
run '95 as a server any
Hello Stanislav,
Monday, December 1, 2003, 5:51:20 PM, you wrote:
> AMT>> Are we discussing this feature's technical or aesthetic merits? Or
> AMT>> both?
> Technical.
> AMT>> foreach ($dom->getElementsByTagname('person') as $person) {
> AMT>> list($firstname) =
> $person->getElementsBy
1 - 100 of 129 matches
Mail list logo
