On Mon, 12 Oct 2009, jval...@eoni.com wrote:
Mark Krenz wrote:
7. PHP Cookbook from 2006
Has mixed examples, some using ereg and some using preg_match
In PHP Cookbook, the only use of ereg I found was in the section
where the books was explaining how to convert from ereg to
preg_match. Or
On Sat, 2 Feb 2008, Antony Dovgal wrote:
On 01.02.2008 23:26, Marcus Boerger wrote:
Sorry for not writing this earlier. So how does this idea sound?
It sounds quite bad.
If you want to do something good for PHP - either respect its rules, or go
away.
Changing the rules to fit your needs
On Sat, 2 Feb 2008, Antony Dovgal wrote:
On 02.02.2008 01:10, Adam Maccabee Trachtenberg wrote:
We change the rules all the time to fit the needs of PHP.
Do we?
Sure. PHP 3 was dual licensed under the GPL. We introduced the Zend
License. We moved the PHP Manual under an Open Publication
On Wed, 30 Jan 2008, Stanislav Malyshev wrote:
Also looking at the discussion, I can see only 6 people involved
(including Dmitry), which most likely means nobody is really
interested in that nowdoc and this is yet another reason not to
add it.
I don't see how 'foo' is anything but
On Fri, 30 Nov 2007, Rasmus Lerdorf wrote:
It is long and complicated and I don't see how anybody could sign this
without getting legal advice. You would also need to pass this by the
legal department of the company you work for. Legal where I work
wouldn't let us sign something like this
On Mon, 10 Sep 2007, BuildSmart wrote:
Perhaps the best approach would be to mimic the ext/mysql functions
and feed them to ext/mysqli function rather than aliasing them
directly but maybe a performance trade-off might be encountered as a
result.
Based on my experiences, if you're keeping to
On Sat, 8 Sep 2007, David Wang wrote:
I don't even have a CVS account yet so I can't commit this patch. I
haven't needed it so I never requested it. However, I will soon in
order to quickly respond to GC-related bugs that might crop up. Could
one be granted to me with the appropriate karma?
On Fri, 9 Feb 2007, Derick Rethans wrote:
On Thu, 8 Feb 2007, Adam Maccabee Trachtenberg wrote:
I read this as saying we're removing the entire ereg extension from
PHP 6. If that's not true, then never mind.
http://www.php.net/~derick/meeting-notes.html#move-ereg-to-pecl
To confim I'm
On Thu, 8 Feb 2007, Nuno Lopes wrote:
convert all ereg*() calls to preg_match(), so that we become
future-proof (ereg is scheduled for removal in PHP 6)
What? When did I miss this? And beyond the obvious reasoning (preg is
better than ereg) why break people?
-adam
--
[EMAIL PROTECTED] |
, Adam Maccabee Trachtenberg wrote:
On Thu, 8 Feb 2007, Nuno Lopes wrote:
convert all ereg*() calls to preg_match(), so that we become
future-proof (ereg is scheduled for removal in PHP 6)
What? When did I miss this? And beyond the obvious reasoning (preg is
better than ereg) why
On Mon, 7 Aug 2006, Pierre wrote:
Compromises are fine. Not implementing certain stuff is fine. Violating
most basic expectations is different. And adding inconsistencies nobody
can understand is imo wrong. I just feel very bad with this movement.
Nobody can understand? Is it not obvious
On Sun, 4 Jun 2006, Andrei Zmievski wrote:
I am sorry if I missed the whole thread. I think that using the
result of __toString() for indexing objects is a bad idea. If we want
to allow this behavior (which is actually useful in some situations),
I'd rather we had a __hash() method or
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_DISK
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 Thu, 9 Feb 2006, Ezra Nugroho wrote:
I have a task that requires bitflag operations. Having only 16 bits to
deal with is really bad (I only care about positive int). Having 32
positive bits in PHP 6 is certainly an improvement, but if I can get all
64, then live would be much better.
It's
On Fri, 6 Jan 2006, Marcus Boerger wrote:
nice nick choice :-)
http://www.omniti.com/~jesus/misc/transformation.jpg
-adam
--
[EMAIL PROTECTED] | http://www.trachtenberg.com
author of o'reilly's upgrading to php 5 and php cookbook
avoid the holiday rush, buy your copies today!
--
PHP
I would like to second this suggestion. I have been playing with the
classmap option and could use the ability to manipulate the object
after instantiation but before it's returned to the user.
-adam
On Tue, 13 Dec 2005, Andrew Yochum wrote:
Hi Matt Dmitry,
Calling the magic __wakeup() func
On Fri, 7 Oct 2005, Derick Rethans wrote:
On Fri, 7 Oct 2005, Rasmus Lerdorf wrote:
Which is why we need the unicode=off switch. I don't think there is any
way we can make Unicode PHP as fast as non-Unicode PHP. For people who
need Unicode support, Unicode PHP will be faster and easier
On Thu, 15 Sep 2005, Leigh Makewell wrote:
Well then I suggest you get out there and find out what you are doing
wrong because there is an increasing number of people out there who are
not happy with how their bugs are being treated.
This is a good place to start.
Let's please stop breaking things just because we find them
aesthetically displeasing.
-adam
On Wed, 31 Aug 2005, John Coggeshall wrote:
So very -1 on anything introducing another way to print stuff. I am
however +1 on turning off everything but ?php from php.ini
John
On Wed, 2005-08-31
On Wed, 24 Aug 2005, Andrei Zmievski wrote:
I took a closer look at this today and RFC 2616 does not specify
whether user agents are supposed to send a charset parameter in the
Content-Type header of the POST request. I did not see any of my
browsers doing so. I think we can safely disregard
On Thu, 18 Aug 2005, Rasmus Lerdorf wrote:
But how does this really help? I don't see how it is possible to
distinguish the namespaced title vs. the non-namespaced ones. My
suggestion here would be that for namespaced nodes the namespace alias
(or perhaps the actual namespace?) becomes the
On Fri, 19 Aug 2005, Rasmus Lerdorf wrote:
Yeah, I agree actually. My real beef is that simplexml and var_dump()
don't place nicely with each other. var_dump() ends up lumping the
namespaced elements in with the non-namespaced elements of the same
name, but when you iterate through things
On Fri, 19 Aug 2005, Sterling Hughes wrote:
I agree. var_dump() should accurately expose the structure of the
simplexml object, if people want to see *everything* they should dump
it explicitly (there is a method in the DOM api to do this?)
You mean other than reserializing the data back as
On Fri, 12 Aug 2005, George Schlossnagle wrote:
9. Radically change all the operator syntaxes. Oh wait, that's Perl
6.0, sorry.
In the same spirit, on my PHP 7.0 wishlist are Unicode operators. :)
-adam
--
[EMAIL PROTECTED] | http://www.trachtenberg.com
author of o'reilly's upgrading to
On Wed, 10 Aug 2005, Marcus Boerger wrote:
i had a chat with Andi about __toString() and i hope that he finally
undestood why a lot of ppl wanted it right from the beginning. To me the
current situation is simply the worst case because noone understnds when it
works and when not (. vs ,).
I can't remember the status of __toString(), but I thought we agreed
improving it was a 5.1 feature, pending an investigation to make sure
we were able to handle this gracefully in the engine.
I don't remember seeing any updates to this code, so I wanted to see
if I missed it, or if we decided to
On Wed, 27 Jul 2005, Sara Golemon wrote:
(B) I don't think SOAP is one of those cases. I would be dissapointed if
SOAP allowed *any* calls to be made when allow_url_fopen is off.
I pretty much take it for granted that people are going to need to
fetch the WSDL file from a remote location.
On Tue, 7 Jun 2005, Andrei Zmievski wrote:
This thread has exceeded the internal per-thread message limit of
ezmlm and has been officially closed. If you find that you have
further energy to contribute, please direct your attention to http://
bugs.php.net/. Have a nice day.
Nazi. :)
-adam
How did PHP end up getting shut out of the Google Summer of Code
project?
http://code.google.com/summerofcode.html
They've got Perl and Python, and even some PHP projects, such as
Gallery, Horde, and Mambo.
Did they e-mail the PHP Group? Did we not jump on this quick enough?
Or was there some
On Fri, 3 Jun 2005, Ilia Alshanetsky wrote:
Perhaps the mentoring FAQ will give you a clue why, specifically the
What is the role of a mentoring organization? portion. :-)
http://code.google.com/mentfaq.html
In other words, we are all too busy to administer the program? That is
a valid
I'm getting a parse error with ext/soap in HEAD. This patch seems to
fix my problem. Can someone review and apply?
http://www.trachtenberg.com/patches/soap_error_handler.txt
Thanks.
-adam
--
[EMAIL PROTECTED] | http://www.trachtenberg.com
author of o'reilly's upgrading to php 5 and php
On Wed, 11 May 2005, Antony Dovgal wrote:
On Wed, 11 May 2005 13:56:46 -0400 (EDT)
Adam Maccabee Trachtenberg [EMAIL PROTECTED] wrote:
I'm getting a parse error with ext/soap in HEAD. This patch seems to
fix my problem. Can someone review and apply?
http://www.trachtenberg.com/patches
On Wed, 11 May 2005, Andi Gutmans wrote:
I just emailed. Adam, you were right and CG()/EG() can't be accessed before
TSRM_FETCH()
So we need to declare the vars, call TSRM_FETCH(), and then assign
values from CG()/EG()?
http://www.trachtenberg.com/patches/soap_error_handler.txt
Right now it
Tony --
In that case, can you recommit a revised patch similar to the one
linked to below? I don't have ext/soap karma.
-adam
On Wed, 11 May 2005, Andi Gutmans wrote:
Yep.
At 05:48 PM 5/11/2005 -0400, Adam Maccabee Trachtenberg wrote:
On Wed, 11 May 2005, Andi Gutmans wrote:
I just
On Thu, 12 May 2005, Antony Dovgal wrote:
On Wed, 11 May 2005 18:49:53 -0400 (EDT)
Adam Maccabee Trachtenberg [EMAIL PROTECTED] wrote:
Tony --
In that case, can you recommit a revised patch similar to the one
linked to below? I don't have ext/soap karma.
Already done, Adam, the lists
On Mon, 4 Apr 2005, Derick Rethans wrote:
FWIW, I don't think maintaining BC is super important here. I don't
believe lots of people are using __autoload() currently, and it should
be pretty trivial to migrate to whatever solution we end up with.
BC is always important.
I didn't say it
On Mon, 4 Apr 2005, David Sklar wrote:
OK, will do. There are a few other things that gcc 4 complains about
which will also need to get addressed in the mythical future when FC 4
is stable. I'll make a list.
FWIW, Mac OS X 10.4 (Tiger) may bundle gcc 4. I believe that should be
out in the
On Sun, 3 Apr 2005, Andi Gutmans wrote:
I don't think the right solution though is to leave the not-optimal
solution in the engine, and create a solution outside the engine. I think
we should find a way to tune the engine so that it works well. Zeev's
suggestion keeps BC. If there are
On Sun, 3 Apr 2005, Marcus Boerger wrote:
Can we get some things straight first (i guess that's the idea of an alpha).
I'd like to reintroduce __toString() since 5.1 is supposed to make it work
again. The patching should be easy enough since we left in most of the
necessary code as we planned
On Fri, 1 Apr 2005, James Ellis wrote:
I think a 5.0.4.1 would be the best way to go (not sure what
versioning to use), as there are no real code changes to justify a
5.05. You could then provide a patch with notes for those with 5.04
installed or they could compile 5.0.4.1
Let's just
On Thu, 24 Mar 2005, Jason Barnett wrote:
...
The obvious problem is:
What comes after i?
ii? iii? iv?
j? k? l?
How transparent is this naming scheme to the user?
Well if it's a simple Roman Numeral system like what I've just done then
we wouldn't really have an issue (except that
On Fri, 4 Mar 2005, Matthew Charles Kavanagh wrote:
The issue in my mind is one of portability. It would be nice, as a
developer working in PHP, to be able to rely on functionality like
encryption (and other unrelated goodies) being available on Joe User's
$5/month webhost who don't go around
Well, that's below 2.5.11, which is what we currently require, so
those folks are already out of luck.
Meanwhile, Mac OS 10.4 is at 2.6.16, so that's okay. I don't have a
10.3 machine with me here at LinuxWorld, so I can't check that.
-adam
On Mon, 14 Feb 2005, Wez Furlong wrote:
Meanwhile,
On Mon, 14 Feb 2005, Wez Furlong wrote:
I was talking with George about this at lunch today. If we really
really do require the new version, then we should add a configure
check to enforce it, otherwise we should use appropriate #ifdefs.
Agreed. If we're requiring it, we need to modify the
On Sun, 13 Feb 2005, Christian Stocker wrote:
There are new features in 5.1, which only run with 2.6 (the new error
handling system, for example, or proper namespace support for SAX).
Those are currently ifdef'd, but it definitively would make the life of
the XML maintainers a lot easier, if
On Sun, 13 Feb 2005, Christian Stocker wrote:
Which is still less than 2.5.11, which is required for 5.0. Therefore
Debian Stable people had to face this problem already with 5.0 ;)
Fair enough. Asking people to upgrade to 2.6.x vs 2.5.11 is minor.
-adam
--
[EMAIL PROTECTED] |
On Sat, 12 Feb 2005, Marcus Boerger wrote:
ups, reading again i see it, it was ReflectionProperty::getDocComment()
There's a generic getDocComment() method, but that just returns the
entire blob. You then need to parse the blog using the preg functions
to extract individual lines. It would be
On Fri, 11 Feb 2005, Andi Gutmans wrote:
Is the XML RPC extension (ext/xmlrpc) still being maintained in PHP 5?
Asking because I heard there were some bugs and I'm not sure if this is due
to the move from PHP 4 to PHP 5. I think it's still based on Expat.
I think this is an extension in need
On Thu, 10 Feb 2005, Greg Beaver wrote:
The best thing internals could do for WSDL is to add a documentation
lexer to reflection, but I would be surprised if this happens - too
complicated unless it's really crude :)
I did something like this using getDocComment() and preg_match() for
On Mon, 7 Feb 2005, Andrei Zmievski wrote:
Hehe... I do hope this is a joke (it would seem rather
closed-minded, otherwise). I don't think anybody would have
bothered if anyone posted PHP code on
e.g. comp.lang.c++(.moderated), in order to illustrate a
point. That would be stupid.
On Tue, 4 Jan 2005, Gareth Ardron wrote:
Somebody just tell me that this isn't exactly expected behaviour and
it's a minor bug
This is a known limitation. I suggest using the reflection classes to
work around this.
class foo {
static function bar() {
print static method!\n;
}
}
Please grant me CVS karma to pear/Services_Ebay. I am working with
Stephen and will commit patches, fixes, etc.
My CVS account is amt.
Thanks.
-adam
--
[EMAIL PROTECTED] | http://www.trachtenberg.com
author of o'reilly's upgrading to php 5 and php cookbook
avoid the holiday rush, buy your
On Thu, 2 Dec 2004, Binam, Jesse wrote:
Let me rephrase that. This is my first contribution to php or any open
source project for that matter, and I have no idea what the process is.
Do I need to write the code first and submit a patch to someone? Do I
need to work with someone since I assume
On Fri, 29 Oct 2004, Paul G wrote:
and what happens in the (admittedly unlikely) case where something else on
the same box depends on that feature being available in libcurl?
They can build two copies of cURL.
-adam
--
[EMAIL PROTECTED]
author of o'reilly's upgrading to php 5 and php
I'm running into an XSLT bug in PHP 4 / Sablotron 1.0 / Windows. I'm
told it's fixed in Sablotron 1.0.1.
Can someone with access to the Windows build scripts please upgrade
Sablotron to Version 1.0.1 in the PHP 4 packages? 1.0.1 came out
almost a year ago, so I think it's safe.
On Sun, 19 Sep 2004, Sam Hobbs wrote:
I think it is reasonable to ask for the one or two lines of PHP code that
solves the problem. As I have said, I did try to do it myself.
foreach ($ContentsDocument-childNodes as $Node) {
$n = $Document-importNode($Node, true);
On Thu, 16 Sep 2004, Sam Hobbs wrote:
Adam Maccabee Trachtenberg [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
Also, are you really using the mysql extension with MySQL 5.0.1? If
so, you need to make sure you pass special flags to MySQL to make it
play nice with the older
On Thu, 16 Sep 2004, Sam Hobbs wrote:
Adam Maccabee Trachtenberg [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
http://dev.mysql.com/doc/mysql/en/Old_client.html
Does the mysql extension use a pre-4.1 client? Perhaps the php
documentation answers that and if so then I don't
On Sat, 28 Aug 2004, Mathieu Bruneau wrote:
I have been playing with the SPL lately and today I ended up playing
with the SimpleXMLIterator.
[snip]
Example:
?php
$xml = testtest1Here we are/test1test2There/test2/test;
$it = new SimpleXMLIterator($xml);
foreach ($it as $k = $v)
On Sun, 25 Jul 2004, Peter Brodersen wrote:
If nobody wants to give an answer to the above, my question would still be:
Is there any way restricting people from retrieving file names (where
open_basedir and safe_mode obviously won't help), besides adding glob to
disable_functions in php.ini?
On Fri, 23 Jul 2004, George Schlossnagle wrote:
Sterling's not as tough as he looks.
That's easy to say when you're 3,000 miles across the country.
Then again, I know you're going to be together in Portland next week,
so there's something for me to look forward to. :)
-adam
--
[EMAIL
Can someone please post when it's safe to start checking my
bugs.php.net folder again? Asshole spammers.
-adam
--
[EMAIL PROTECTED]
author of o'reilly's upgrading to php 5 and php cookbook
avoid the holiday rush, buy your copies today!
--
PHP Internals - PHP Runtime Development Mailing List
On Tue, 20 Jul 2004, Derick Rethans wrote:
On Tue, 20 Jul 2004, Adam Maccabee Trachtenberg wrote:
Can someone please post when it's safe to start checking my
bugs.php.net folder again? Asshole spammers.
I blocked the IP, removed all the spam comments and sent an abuse to
ev1.net (the IP
On Fri, 16 Jul 2004, Christian Stocker wrote:
I didn't blame you and there are good reasons to not to port it. But for
BC, maybe someone will do it anyway... OTOH the switch to ext/xsl isn't
that hard and you gain a lot of speed improvements ;)
I think the only difficulties you'd run into is
On Tue, 13 Jul 2004, Daniel Crookston wrote:
So, am I being lazy, have I missed some docs on the web regarding how to
be useful, or how to become familiar enough with the PHP code to start
lending a hand with the debugging? Or are we expected to learn it
ourselves, on our own, in order to be
On Mon, 12 Jul 2004, John Coggeshall wrote:
Not to bust everyone's bubble here, but frankly what is the point of a
90-100+ thread on this? I mean can't this just be implemented as a PHP
function without all this discussion?
Maybe we should name the function bikeshed()? :)
On Thu, 8 Jul 2004, Marc Richards wrote:
Are you saying PHP will never introduce an operator that doesn't already
exist in a large number of other languages?
I certainly hope not. (Well, I guess === and !=== are exceptions to
this statement.)
Compound Ternary operator:
$a = $b ?: $c;
You
On Wed, 30 Jun 2004, Gareth Ardron wrote:
Does the examples I gave you before not count ?
Yes. It does not count.
in this case, the __destruct() function within someOtherClass does
absolutly bugger all.
You can't reference one object from another's destructor. PHP makes no
promises about
On Sun, 20 Jun 2004, Zeev Suraski wrote:
I don't think it reflects on the quality of PHP 5. It does reflect on the
fact that migrating is a bit scary.
Agreed, but I think that anything we can do to help mitigate these
fears will help spur PHP 5 adoption.
Deciding to migrate is about reward
On Sat, 19 Jun 2004, Lester Caine wrote:
need to sort out how to replace the 'extra' bits. Not done a
comprehensive test, but php.net working fine on W2k/Apache2/PHP5 as was
probably expected. The fun will come with running an update ;)
I just set up phpweb on Mac OS X / Apache 1.3 / PHP 5
On Thu, 17 Jun 2004, Jason Garber wrote:
Is being able to have a comma at the END of an array definition a supported
feature, or an undocumented feature that should not be used?
If I remember correctly, Zeev or Andi specifically added it as a
result of a user request, so I'd say it's an
On Wed, 16 Jun 2004, Hartmut Holzgraefe wrote:
1) strrpos('abcd', '') returns 4. Expected FALSE
Although one could argue whether searching for empty
strings makes sense at all the result is not completely
wrong. There *is* an empty string at the end of the haystack ...
And at the beginning
On Wed, 16 Jun 2004, Hartmut Holzgraefe wrote:
It should still find the *last* emtpy string, not the first,
shouldn't it? ;)
Yup. I think we've now spent more time discussing this function than
people have spent using it. :)
-adam
--
[EMAIL PROTECTED]
author of o'reilly's php cookbook
avoid
Right now, if you're using the pre-built Windows binaries, you can use
cURL to make an SSL request, but you can't use an https stream.
I'm guessing from this that OpenSSL is already on the box that creates
the binaries, and we just need to modify the build script to enable
it. If somebody had the
On Wed, 9 Jun 2004, Adam Maccabee Trachtenberg wrote:
Right now, if you're using the pre-built Windows binaries, you can use
cURL to make an SSL request, but you can't use an https stream.
Um. Nevermind. I am an idiot.
-adam
--
[EMAIL PROTECTED]
author of o'reilly's php cookbook
avoid
On Tue, 25 May 2004, Andi Gutmans wrote:
I'd like to release RC3 on Thursday/Friday. I believe this to be the last
RC before we can release.
If anyone has bug fixes to commit please do so within the next couple of days.
I have a few DOM element and attribute validation bug fixes I need to
On Mon, 24 May 2004, Christian Schneider wrote:
Jason Garber wrote:
Based on the above example, the $oSession-__destruct() method relies on
the $oDB object still being usable. How can this be structured to
ensure that the DB object does not get released first?
It can't.
Adding
On Mon, 24 May 2004, Lukas Smith wrote:
unless you manually unset the objects in the order in which you want
them to be destructed.
Right. That'll also work. :)
-adam
--
[EMAIL PROTECTED]
author of o'reilly's php cookbook
avoid the holiday rush, buy your copy today!
--
PHP Internals - PHP
On Tue, 20 Apr 2004, George Schlossnagle wrote:
On Apr 20, 2004, at 3:22 AM, Derick Rethans wrote:
On Mon, 19 Apr 2004, Sterling Hughes wrote:
mo compile errors mo better.
But NOT for normal methods!
I agree with Derick. Compile errors for interfaces methods good.
Compile errors
On Thu, 15 Apr 2004, Andi Gutmans wrote:
I held RC2 because I thought this was a critical engine bug. It happened
because instead of not implementing NULL you implemented it without a body.
Right now I changed it to NULL which means that any clone either via
clone or compatibility_mode will
On Tue, 13 Apr 2004, Marcus Boerger wrote:
Hello Marcus --
This brings us back to an old problem the severity levels are inconsistent.
And further more we decided some time back that E_ERRORs shouldn't be
converted to exceptions because of a few E_ERRORs that might not be
continuable. From
On Tue, 13 Apr 2004, George Schlossnagle wrote:
Is there a reason not to move non-continuable E_ERRORs to E_WARNINGs?
This prevents us from adding another severity level and also allows us
to make all E_ERRORs fatal in the process.
This is a huge bc break. Raising the severity on
On Tue, 13 Apr 2004, Marcus Boerger wrote:
In PHP 4, E_ERROR is fatal. In PHP 5, E_ERROR is (currently) also
fatal. This always happens regardless of any exception handling.
With exceptions, we have the ability to modify E_ERRORs to be
non-fatal.
Not at the moment.
Ah. Okay. I guess I
On Tue, 13 Apr 2004, George Schlossnagle wrote:
On Apr 13, 2004, at 4:52 PM, Adam Maccabee Trachtenberg wrote:
I guess I'm confused about why some E_ERRORs are now able to be
handled in userland, but only by using exceptions.
It's important to note that this is now technically feasible
On Wed, 14 Apr 2004, Marcus Boerger wrote:
If the developer catches it, they handle it. If they don't, PHP
catches it and issues a fatal error.
I am not a friend of PHP catching exceptions and converting them to
E_ERRORs. Just have an uncaught exception message as we have now.
And no way
On Wed, 14 Apr 2004, Marcus Boerger wrote:
Hello Marcus --
This is actually a pretty nasty side effect of throwing exceptions in
ctors because these two lines have *very* different results if they
fail:
$db = new SQLiteDatabase();
$db = sqlite_open();
sqlite_open returns a resource
On Mon, 12 Apr 2004, Ilia Alshanetsky wrote:
There is 1 problem with this approach. Currently an uncaught exceptions
results in a fatal error (E_ERROR) meaning that if a particular method throws
an exceptions it MUST be caught otherwise the script will terminate. Having
to wrap some methods
On Mon, 12 Apr 2004, Derick Rethans wrote:
On Mon, 12 Apr 2004, Adam Maccabee Trachtenberg wrote:
How can anyone rationally design an application when half of their
problems issue errors and the other half throw exceptions? That's a
recipe for disaster.
Exactly the reason why nothing
On Mon, 12 Apr 2004, Ilia Alshanetsky wrote:
On April 12, 2004 10:58 am, Adam Maccabee Trachtenberg wrote:
Still, you shouldn't be ignoring E_WARNINGs unless you have a good
reason.
There are plenty of situations where E_WARNING can be safely ignored. And even
more situations where
On Mon, 12 Apr 2004, Greg Beaver wrote:
Adam Maccabee Trachtenberg wrote:
I am willing to concede that SQL parse errors aren't the best example
here, but that doesn't mean extensions should never throw exceptions.
If a user has written code expecting it to work in PHP 4 and PHP 5
On Mon, 12 Apr 2004, Andi Gutmans wrote:
I think the main reason for all of this disagreement, is because PHP
(pre-exception state) is not consistent with its error levels. As mentioned
here, sometimes relatively serious errors are E_WARNINGs and some less
serious errors are E_ERRORs.
I
On Sun, 11 Apr 2004, John Coggeshall wrote:
As a matter of consistency, I would like to suggest that for those
extensions which have a OO/procedural syntax that the non-fatal errors
generated by those extensions be thrown as Exceptions when called from
an OO syntax. I have already committed
On Thu, 8 Apr 2004, Magnus [iso-8859-15] Määttä wrote:
debug_backtrace() used to print out arguments to functions, but does not
anymore. Is this desired behavior ?
I discovered this least night and it is already filed as a bug:
http://bugs.php.net/bug.php?id=27397
I'm hoping it's a bug, not
On Tue, 6 Apr 2004, Ben Ramsey wrote:
Any help at all is much appreciated. We cannot launch this site until
this issue is resolved, and don't ask me to revert back to a stable
version of PHP or we will have to modify much code throughout the site. ;-)
You will significantly improve your
On Sat, 3 Apr 2004, Ilia Alshanetsky wrote:
Given our history with bundled libraries (gd, expat, sqlite, etc...)
we always tend to lag (often quite a bit) behind the official stable
release even if we do sync the libraries relatively frequently the
release cycle of the libraries themselves is
On Fri, 2 Apr 2004, Derick Rethans wrote:
*casting* works fine, we just don't do it automagically:
print (string) $obj;
Not anymore:
class foo {
function __toString() {
return I am a string.;
}
}
$foo = new foo;
print (string) $foo;
Object id #1
-adam
--
[EMAIL PROTECTED]
author
On Mon, 29 Mar 2004, Sebastian Bergmann wrote:
ccache gcc -Iext/mysqli/ -I/usr/src/php/php5/ext/mysqli/ -DPHP_ATOM_INC
-I/usr/src/php/php5/include -I/usr/src/php/php5/main -I/usr/src/php/php5
-I/usr/src/php/php5/Zend -I/usr/include/libxml2 -I/usr/X11R6/include
-I/usr/include/freetype2
On Tue, 23 Mar 2004, Rasmus Lerdorf wrote:
they are all in sync. For example, Derek Ford's simplexml-related message
to internals last week(*) worries me somewhat. He passed on what looks to
be some basic brokeness in the extension which nobody has addressed so
far.
(*)
On Fri, 5 Mar 2004, Antony Dovgal wrote:
On Fri, 05 Mar 2004 15:07:42 +0200
Andi Gutmans [EMAIL PROTECTED] wrote:
Hey,
I've fixed all of the major bugs I wanted to get done for RC1.
What about this bug - http://bugs.php.net/?id=27504 ?
It looks as rather major to me.
Or this one?
1 - 100 of 151 matches
Mail list logo
