Dmitry Stogov wrote:
It is bad practice to use echo $float or var_dump($float)
because they depends on php.ini settings.
You should use printf() of number_format() for deterministic result.
The float formatting algorithms were changed because of
licensing issues and new ones are not 100% compat
Hi,
Going over the todo list I wanted to bring up a few topics once again
for review/discussion (not flaming):
http://oss.backendmedia.com/PhP60
# Unicode
3. remove old parameter parsing API and replace with one that
supports unicode related functionality
I just want to remind that when
Lukas Kahwe Smith wrote:
Mark Wiesemann wrote:
This was just a friendly note for Sebastian and other mentors, e.g. to
avoid that maybe Google itself ranks people like Thomas Koch next year
down because their 2007 application was marked as "spam" (<= in Google's
interpretat
Ron Korving wrote:
Hi,
returning array('5' => 'Foo', '10' => 'Bar') from a SoapServer handler class
ends up as array(0 => 'Foo', 1 => 'Bar') at the client end. I can hardly
imagine this being a feature, but maybe someone can tell me if this is
somehow wanted or inevitable behavior.
I assume
Mark Wiesemann wrote:
This was just a friendly note for Sebastian and other mentors, e.g. to
avoid that maybe Google itself ranks people like Thomas Koch next year
down because their 2007 application was marked as "spam" (<= in Google's
interpretation).
Good point. We will provide feedback to
Mark Wiesemann wrote:
The most important sentence of this paragraph is:
| Use the "Ineligible" link only for applications that are spam.
Sorry about that. You have to realize that the SoC Mentor interface is
utter crap. So we are trying to make the best of the available features
in order to
Andrey Hristov wrote:
Hi,
Lukas Kahwe Smith wrote:
Robin Ericsson wrote:
On 3/21/07, Bankó Ádám <[EMAIL PROTECTED]> wrote:
The project is existing, I'm doing it for about a year and a half, and
SoC is way I can spend more time on it in the summer.
If there is someone willing t
Robin Ericsson wrote:
On 3/21/07, Bankó Ádám <[EMAIL PROTECTED]> wrote:
The project is existing, I'm doing it for about a year and a half, and
SoC is way I can spend more time on it in the summer.
If there is someone willing to something, and someone else is paying
for it, let him do it. Why s
Guilherme Blanco wrote:
As I mentioned before, the best ORM tool I've notice is Doctrine, but
it has some issues that I can list if necessary. The point is not to
BTW: the lead author of Doctrine aready submitted an SoC project idea
for php.net on googles website.
regards,
Lukas
--
PHP Int
Stanislav Malyshev wrote:
Thoughts?
This might work, still not sure if we really want that in PHP. On one
side, it's cool, on other side closures can develop into a very messy
code :)
Yeah well .. for the single task of callbacks they are great and prevent
a lot of messiness .. I think it
Tony Bibbs wrote:
Sorry, I wasn't clear on this. Creole is the DB abstraction layer on top
of the "old extensions". The older versions of Propel were implemented
that way. The new beta version uses PDO dicrectly (i.e. minus Creole)
and that showed significant speed improvements over prior ve
Tony Bibbs wrote:
I agree. I'm a user of Propel (http://propel.phpdb.org) which is in the
user space as you suggest and I think it works fine. The current beta
version of Propel uses PDO so execution speed isn't really a huge
FYI: You are mistaken if you think that moving from the old exte
Hi,
just to clarify .. from your comments I am quite hopeful in your proposal.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Bankó Ádám wrote:
Pure C code has access to PHP5's low level object API, so it can produce
a really intuitive interface (object persistence), that you can't do
from PHP code. C code uses a bit less memory and a lot less CPU time
I would hope that the solution for "low level object API" would b
Bankó Ádám wrote:
I'm an interested student with a project idea for the PHP.net Google
Summer of Code.
I'm thinking about a native ( compiled from C ) ORM extension for PHP. I
don't need to explain how useful and important it is in modern web
applications / frameworks.
IMHO a full ORM belongs
Marcus Boerger wrote:
Hello Ilia,
of course we can. The question is how do we find a student for ideas we
have?
one we have a fairly complete overview of ideas .. we can have a few of
us blog the world :)
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscri
Derick Rethans wrote:
On Thu, 15 Mar 2007, Antony Dovgal wrote:
Hannes also has some ideas on improving our bug tracker as a GSoC project.
And I am thinking about this:
http://derickrethans.nl/wanted_dbgp_xdebug_client.php
Do you guys think that would qualify as php project as well?
Hell y
Marcus Boerger wrote:
Hello Lukas,
for now simply add the project here: http://de.php.net/ideas.php
Once the selection process startswe will discuss it in detail.
I do not have karma for this. I guess for "ideas" that already have a
student and mentor, we do not really need them on the idea
Nuno Lopes wrote:
I think that's a good idea. I would say you should go ahead and add the
idea to our SoC page (http://php.net/ideas.php).
BTW, we should start gathering ideas because the summer is not far away.
Indeed. Actually Students have to submit their proposals by March 24. So
now is t
Hello,
Konsta asked me to forward this email, as he is having issues posting to
internals. Anyways I should also add that I would be willing to mentor
this proposal.
Obviously Doctrine is not part of an official (sub)project of php.net.
He did try to get the package into PEAR, though there w
Hannes Magnusson wrote:
On 2/25/07, Sebastian Bergmann <[EMAIL PROTECTED]> wrote:
Hannes Magnusson wrote:
> I am not really a politics fan, but if we are going to list project
> not under "the php.net umbrella" (PHPUnit isn't a php.net project
> anymore, is it?) don't we then have to list _all_
Hello,
I am consuming some Java provide webservices. In some cases we get
SOAPFault instances, that I would like to massage a bit, since I do not
like the structure or format in the generated SOAPFault (for example it
does not set the error code properly). However since there are no
setters,
Derick Rethans wrote:
On Tue, 20 Feb 2007, Arnold Daniels wrote:
I'm also very in favor of this, though I like it much better if it would use
the same config file as `file` uses. Otherwise it's quite confusion where to
config magic and hard to understand why the result differs.
The idea is to
Antony Dovgal wrote:
On 02/15/2007 06:24 PM, Ilia Alshanetsky wrote:
I think it makes sense for RC1 and few of the first level releases
but not the very closely spaces RC4+ where there are virtually no
changes between the releases.
I believe it doesn't matter which RC is that, it helps to d
Hello,
This is turning into a major headache for me. The handling of sequences
in ext/soap seems somewhat problemematic. I have come across the
following bug report which I have reopened:
http://bugs.php.net/bug.php?id=36226
Essentially I see 3 cases:
1) sequence is empty
2) sequence has one
LAUPRETRE François (P) wrote:
The other reason why I want a dedicated RFC space is history. Every day, you see messages
saying 'I don't remember...', 'what did we decide... ?'. There is no place with decision
history. So, the same subject is regularly discussed again and again.
@Steph: Could
Mehdi Achour wrote:
Thank you all for your replies, I'm happy to see that the snowball
effect started!
Just make sure that you take this momentum and directly contact people
who's offers you want to take up so that real world effect can be
derived from all of the offers.
regards,
Lukas
--
Philip Olson wrote:
There are 137 open documentation bugs and many of these require PHP
internals intervention. I don't know the best way to help that happen
aside from maybe going through them all and updating the summaries (and
appending categories to those summaries) but then what? A questi
Rasmus Lerdorf wrote:
Perhaps we can do more though. Maybe you guys could periodically update
internals on problem areas in the docs. Places where you feel things
are vague and really could use the guy who wrote the code to get off his
ass and explain how it works. Or maybe we could get every
Derick Rethans wrote:
But do note that late static binding would be greatly appreciated.
Yes, but that'd be something for 6 i think.
I just nocticed its already on the php6 todo list as:
re-use the "static::" keyword to do runtime evaluation of statics.
http://oss.backendmedia.com/PhP60
Fo
Olivier Hill wrote:
On 2/9/07, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
Overall I would say, while painful I do not really see the point in
investing development resources into keeping ereg alive, since its just
a duplication of efforts. Then again I have avoided ereg since PHP4
day
Antony Dovgal wrote:
As far as I understand, the point is that ereg does/can not support
Unicode, therefore we cannot keep it PHP6, which major feature is
Unicode support.
_BUT_ it is possible to use PCRE to "emulate" ereg, so yes, the existing
code
should continue working.
Well I remember
Jim Wilson wrote:
Is there a PHP/Zend bug-tracking system that can be used to record and
moderate these requests (like a Bugzilla server somewhere)? Or is there a
wiki or forum that that can be devoted to the change-process?
(Sorry for these n00b questions - I'm a long time PHP hacker - but I've
Lukas Kahwe Smith wrote:
Ilia Alshanetsky wrote:
On 9-Feb-07, at 1:49 AM, Lukas Kahwe Smith wrote:
1. on-the-fly static properties (mike)
It was already discussed on the mailing list in the past and declined.
Hmm I will search the archives, but I am not aware that this was declined
Ilia Alshanetsky wrote:
5. pat3 "OpenLDAP C API cleanup patch" and pat44 "LDAP control
support"
The patch is where?
http://marc.theaimsgroup.com/?l=php-dev&m=115635520414869&w=2
I should have mentioned that many of the items have links that are
listed on the PHP 5.2 todo page:
http://o
Ilia Alshanetsky wrote:
On 9-Feb-07, at 1:49 AM, Lukas Kahwe Smith wrote:
1. on-the-fly static properties (mike)
It was already discussed on the mailing list in the past and declined.
Hmm I will search the archives, but I am not aware that this was declined.
regards,
Lukas
--
PHP
Michael Wallner wrote:
1. on-the-fly static properties (mike)
I didn't request these
FYI, the names in parenthesis are the person I figured was most likely
to implement the given feature and not who requested it necessarily.
Anyways, a lot of people "abuse" the comment system on the tod
Hello,
On the heels of the 5.2.1 release I just wanted to bring up the
following todo items that have been on the 5.x todo lists since ages.
Are these still alive? Have they been done? What would be a sensible
target version?
Especially the "on-the-fly static properties" is much requested.
Christopher Jones wrote:
steve wrote:
> Oh, and allow persistent connections in db apis again (like mysqli).
It might happen. Wez Furlong was contemplating a persistent
connection implementation for the generic PDO interface following
on from the persistent connection model in the oci8 extensi
Christian Schneider wrote:
My personal summary of this thread is: We won't have syntactic sugar for
common things like arrays, named parameter emulation and the like ever
because it will be killed by the "we already have a way of doing this"
and the "you cannot look it up" argument. Shame, tha
Ilia Alshanetsky wrote:
On 4-Feb-07, at 1:14 PM, Pierre wrote:
On 2/4/07, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
I personally find array extremely clear, in recent weeks I had to do
A LOT of JavaScript work where the array syntax works in a manner you
suggest for PHP and its a massive pai
Steph wrote:
On 2/4/07, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
I personally find array extremely clear, in recent weeks I had to do
A LOT of JavaScript work where the array syntax works in a manner you
suggest for PHP and its a massive pain. It does not make for a very
clear code. I think t
Marcus Boerger wrote:
Hello Andi,
it is a bit harder to read and not the php way imo.
I agree with Marcus.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
I just wanted to ask everybody working on PHP6 to take the time to look
over the PHP6 todo list [1] and note any items that need to be updated.
As always either let me know if you need a login or simply send me what
you think needs changed. I am sure that a few items can probably be
marke
Wez Furlong wrote:
On 1/13/07, Lukas Kahwe Smith <[EMAIL PROTECTED]> wrote:
SQLite does not natively support prepared statements anyways.
Yes it does :)
Ah, I got thrown off by the use of the word "precompile" which they also
used to describe dumps of the byte code gene
Stefan Esser wrote:
SELECT xyz FROM abc WHERE product_id IN ( 1,2,3,4,5) <- the list having
dynamic lenght
They have worked in PEAR::DB and some other DBAL's, as a result a lot of
people have come to think of prepared statements as a sprintf() replacement.
By the nature of prepared stateme
Stefan Esser wrote:
Hello Lukas,
Maybe I am missing something. If you are talking about dynamic query
generation in stored routines, then I would think that people who read
the advice over dynamic query generation for PHP, that they would
hopefully also apply those practices to when they are wr
Stefan Esser wrote:
While it is true that the PHP script is not subject to SQL injection
when the application does not build parts of the query based on
untrusted userinput it is not true that you are not at risk.
Ever heard of stored procedures? And precisely of SQL injection in
stored procedur
Andi Gutmans wrote:
Btw, today I never recommend running mod_php on Windows and always point
people to CGI or existing FastCGI implementations.
Well a lot of people develop on windows and deploy on Linux with
mod_php. For these people it probably makes more sense using mod_php on
windows sti
Hi,
while on the train I tried to strat up 5.2.0RC2 on windows and ended up
with Apache complaining about the pdo, pdo_mysql, pdo_sqlite and sqlite
extensions during the load process. I will try to investigate further
tomorrow.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailin
Stanislav Malyshev wrote:
I disagree - you describe scenario where the user chooses to
insufficiently or wrongly sanitize the data, and since tainting can not
protect from it you say tainting is not useful. However, as I already
said, tainting is not supposed to do that. It's like blaming comp
Hi,
I assume its not possible to implement this as a PECL extension. As an
extension it would make sense though even in this b&w approach as it
would then truly be an optional tool you can use like a debugger without
cluttering the core.
regards,
Lukas
--
PHP Internals - PHP Runtime Develop
Stanislav Malyshev wrote:
Then I see little need for having in PHP. All it means that developers
now need to write a untaint wrapper around all incoming input to shut
PHP annoyances up. I can guarantee you a tons and tons of code that
No, they need to use recommended ways to work with variabl
Jeff Moore wrote:
On Dec 19, 2006, at 10:53 AM, Ilia Alshanetsky wrote:
Bottom line is that does not, there are plenty of Perl application
supposedly safe from XSS due to tainting while in reality are
trivially exploitable via XSS due to the fact validation regex which
does the un-tainting o
Ilia Alshanetsky wrote:
Wrong again, different contexts have different validation criteria,
unless you consider that tainting in PHP wont work. What's safe to print
on screen may not be safe to execute or pass to the database etc...
Ilia is right here, this is the key concern with this propos
Alain Williams wrote:
I propose to give a partially working tool that helps in the majority
of cases. I am aware that it will not be a panacea but that it is preferable
to nothing.
A non context aware taint will fail in the majority of use cases.
regards,
Lukas
--
PHP Internals - PHP Runtim
Hi,
why do I get warnings when I have failures in my ext/soap ctor?
try {
$client = new SoapClient('http://i_dont_exist.com/some.wsdl',
array('exceptions' => true));
} catch (Exception $e) { }
I guess even without the 'exceptions' => true it should always return
all issues as an exception.
Hi,
To me some of Ilia's arguements do not make sense. Ext/filter has the
same danger of creating a false sense of security. The arguements that
did make sense to me are about the issue of (un)tainting being directly
tied to the context in which the variable is being used.
This is a problem
Ilia Alshanetsky wrote:
In theory, you need to consider that many ISPs and users will interpret
taint mode == secure and enable it causing much grief to distributable
application writers who need to accommodate every environment.
actually i dont think this is a valid argument. people will qu
Marcus Boerger wrote:
Hello Richard,
The "#" is needed for CLI mode - thus we won't remove it. In fact we
will not do anything that would cause BC problems. Also there is no
escaping issue with "\". If there is than it is outside of PHP. In
other words:
- "\" is the only single character reachab
Patrick Mueller wrote:
There would typically be a one time 'hit' in your code for a long,
prefixed named used as a constructor, or possibly a static method called
on a factory. After that, if you're dealing with object instances, then
instead of function names (which would need to also use a
Ron Korving wrote:
- First of all, people use their classes a lot more than PHP core classes,
and so prefixing application classes is a big burden compared to prefixing
PHP core classes.
Its quite trivial .. all people need to do is stick a single underscore
into their class name [1]. Thats al
Greg Beaver wrote:
Adam Maccabee Trachtenberg wrote:
I am trying to use go-pear under 5.2 (latest snap) on Windows XP. The
script loads correctly, but when it tries to do the install, I get a
number of errors. (See below.)
Since 5.2 is about to go out the door, I thought I should post an
messag
Glenn Richmond wrote:
look and see if I can come up with a fix in the mean time. Should it be
re-logged as a bug to get it some more attention in the future?
more bug reports are not going to help .. just append the existing one
with a patch.
regards,
Lukas
--
PHP Internals - PHP Runtime D
Glenn Richmond wrote:
No, it's never worked as far as I know, but it doesn't mean it's not a
bug. The session functions shouldn't have to be reset every time
session_write_close or session_destroy is called. It's been logged
previously at: http://bugs.php.net/bug.php?id=32330. It's also a
con
Glenn Richmond wrote:
i.e. It still knows that it's a custom defined handler, but the
references to the functions are gone. If I make a call to
session_set_save_handler after the first session_write_close, the
problem goes away. Of course, this isn't practical for a large number of
sites.
And
Glenn Richmond wrote:
Hi guys,
Just wondering what the status of the user-defined session handlers is?
I've tested with 5.2rc4 and there is an issue that the references to the
user functions get erased when the user calls session_write_close or
session_destroy. This means that the system revert
Richard Quadling wrote:
+1 - As an aside, it would be extremely useful to have the PEAR
classes marked as NON strict (in some way) until they are. I know this
is outside of the core, but using E_STRICT already means you have to
toggle off E_STRICT for PEAR. MAYBE STRICT (e.g. strict class PEAR
{
Wez Furlong wrote:
I don't think we need to set any firm ground rules for the deprecation
timeline but should consider each change individually. A reasonable
rule of thumb is to remove deprecated features no sooner than 1 minor
release after the deprecation notice was added. Ideally, it should
Zeev Suraski wrote:
Ilia,
I think Wez's suggestion is the most practical one. Let's make sure we
haven't introduced any fatal errors into 5.2 (and demote them to
E_STRICT for now), and handle the rest of the suggestions afterwards.
+1
I guess this is the best we can go. It might cause some
Ilia Alshanetsky wrote:
Actually it is no break at all, take PHP4 code move it to PHP and you
won't even see the warning because E_STRICT is not even shown by default.
haha
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.
Derick Rethans wrote:
On Mon, 23 Oct 2006, Lukas Kahwe Smith wrote:
Pierre wrote:
On 10/23/06, Pierre <[EMAIL PROTECTED]> wrote:
Hello,
On 10/23/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
Use of mktime(0) and alike is improper use of the function, more over
generally it c
Pierre wrote:
On 10/23/06, Pierre <[EMAIL PROTECTED]> wrote:
Hello,
On 10/23/06, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> Use of mktime(0) and alike is improper use of the function, more over
> generally it can be traced to an undesired code behavior.
Which is? mktime(0) is just like mkti
Derick Rethans wrote:
On Sun, 22 Oct 2006, Richard Quadling wrote:
With the recent discussion on E_STRICT and the waste of cpu cycles ...
Why is mktime(0, 0, 0, 0, 0, 0) generating E_STRICT?
What is unstrict about this?
Why is important to use time() instead?
It's quicker.
as I just said
Hi,
Its been a while since I or anyone else has done any updates on the PHP
6 todo page [1]. I know that some of the todo items are big enough that
even with the many commits being made to HEAD they will take a bit
before they will be finished.
Anyways I just wanted to ask if someone who has
Marcus Boerger wrote:
That said I can only repeat here what I said earlier on IRC. Lets do things
right and make the more complex OO rules as E_STRICT and create new severity
level E_DEPRECATED. E_STRICT will then only be used for 'pedantic' OO rules
while E_DEPRECATED will be used for stuff tha
Ilia Alshanetsky wrote:
It is working code, its far from perfect given that it makes little
programatic sense and does break all known OO conventions.
Being allowed to break these "known OO conventions" is a major feature,
which has established PHP as a rapid prototyping language. Having some
Ilia Alshanetsky wrote:
its funny that ext/mysql is supposed to stay around for BC reasons
even in PHP6, yet it has known unsolvable security issues.
Such as?
for example, it does not support the new more secure authentication
protocol.
regards,
Lukas
--
PHP Internals - PHP Runtime Devel
Edin Kadribasic wrote:
I'm sure there are more examples of how PHP 5.2 and newer will enforce a
different "spirit" that smells more off a static programming language.
and these changes are being made in a minor release!
its funny that ext/mysql is supposed to stay around for BC reasons even
Hi,
I just want to say once again that all hell is going to break loose once
we release 5.2.0 as stable thanks to the various fatal errors we are
adding for perfectly working code that breaks OO theory.
I am talking about this change:
http://marc.theaimsgroup.com/?l=php-dev&m=114734977430980&
Ilia Alshanetsky wrote:
I may be somewhat out of the loop, since I have been cut of from IRC and
the mailing lists for a week. So maybe there were some discussions not
done on this list that I have missed. The number of commits to the 5_2
branch over this one week period of time look kind of s
Edin Kadribasic wrote:
Edin Kadribasic wrote:
Stanislav Malyshev wrote:
The vote is should OO strictness (fatal error on changing function
arguments in derived classes in this case) be removed or kept.
I think fatal error should be definitely removed or the rules be at
least relaxed sufficie
Ralph Schindler wrote:
In the spirit of fopen's optional [, bool use_include_path].. is this
something that can be added to is_readable?
ie:
bool is_readable ( string filename [, bool use_include_path] )
we can always dream ..
so far the answer has been that this parameter should never have
Michael Wallner wrote:
3, 2 [+1] (remove)Mike, Pierre, Edin (Robert Cummings, Bertrand Gugger)
1, 1 [+0] (nonfatal) Zeev (Richard Lynch)
3, 0 [-1] (leave) Sebastian, Ilia, Derick
BTW I think even if Marcus has not voted yet he is sure to be in the
leave as in CVS camp :)
rega
Michael Wallner wrote:
Michael Wallner wrote:
I'd therefore like to conduct a serious vote on this issue.
[X] (+1) please remove that redundant strictness again
[ ] (-1) leave as it is, we need strict OO implementation
[ ] ( 0) what the hell are you talking about?
3, 2 [+1] (remove)Mi
Hi,
I am in a bit of time trouble and I unfortunately do not have the same
routine in testing patches (something I really need to setup). But I
promised Ilia to get the following patch tested:
http://bb.prohost.org/patch/pg.txt
If someone could test it out with PostgreSQL 8.0.8 or 8.1.4 I wou
Derick Rethans wrote:
On Sun, 24 Sep 2006, Ron Korving wrote:
In this case, wouldn't E_NOTICE make more sense? E_STRICT kind of indicates
that certain behaviour is deprecated, right?
Not really, E_STRICT is for when you're doing something that you
shouldn't. In my opinion that includes using
Hi,
it seems that PHP was not updated to make use of PQescapeStringConn from
libpq. Looking at ext/pgsql and pdo_pgsql they both still seem to be
using PQescapeString.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
in my on going effort to make PHP todo management more transparent I am
wondering what are the current open todo items for PHP 5.2?
Obviously bug fixing. Filter ext needs some love on the function names
and some of the parameters. That makes me wonder about the other newly
bundled extens
boots wrote:
Well, with unicode semantics enabled, many PHP applications that have
not been designed with PHP6+unicode in mind are likely to break. On
the other hand when semantics are off, those applications may work
just fine. The other reason could be that unicode enabled PHP will be
n
Matthias Pigulla wrote:
Hi all,
I'm afraid that recent changes in filestat.c [1] that were meant to fix
a bug [2] with file_exists() also altered the behaviour of
is_readable(). According to the docs [3] [4], is_readable should *not*
take safe_mode limitations into account, whereas file_exists s
Steph Fox wrote:
Hi Andi,
Rock vs hard place - RC's were announced on php.net and distributed via
the download page for some several months in the past. It led to a lot
of user confusion, particularly when there were any binary compat
breakages, and the RMs went back to simply announcing RCs
Hi,
I spend some time this morning adding some more items to the upgrading
guide:
http://pooteeweet.org/public/README.UPDATE_5_2.diff
Unfortunately I got no feedback to my request for comments of what to
add to the upgrading guide. Aside from the blog posts by Derick and Mike
all additional
Andi Gutmans schrieb:
Yep I completely agree.
Although PHP is a volunteers project, the development team represent the
project, and should therefore try and be as professional as possible (in the
many things that encompasses).
I agree with the general request, though I would be hesitant to comb
Lukas Kahwe Smith wrote:
Hi,
Reading Derick's post [1] about some new notices in 5.2 reminded me
again that it is very important that everybody that notices little
issues like these that they add a note to the upgrading guide [2]. If
you do not have time to write something up you
Hi,
Reading Derick's post [1] about some new notices in 5.2 reminded me
again that it is very important that everybody that notices little
issues like these that they add a note to the upgrading guide [2]. If
you do not have time to write something up yourself, please at least
notify this lis
Matthias Nothhaft wrote:
I would like to commit changes to the LiveUser and LiveUser_Admin packages.
Lukas told me to ask for cvs access. Thanks.
Aye, he has my blessings :)
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsu
Pierre wrote:
Hello,
On 8/10/06, Michael Walter <[EMAIL PROTECTED]> wrote:
Yeah. It is problematic that the application has no chance of dealing
with the errors itself (consider e.g. php-shell which has to go great
lengths to prevent fatal errors from user code leading to php-shell's
terminati
Michael Walter wrote:
Hi,
right now, PHP triggers fatal errors e.g. when accessing private
members or calling nonexistant functions. Since this is problematic
for obvious reasons, what technical reasons are there for that
behavior, and is there a chance that this behaviour will change in a
futu
Hi,
replying to internals ..
this was originally a comment made on the following site:
http://oss.backendmedia.com/PhP60
> [EMAIL PROTECTED] writes:
>
> What about improving the autoload mechanism ?
> Suggestions :
>
> - When autoload() is called, it is impossible to know if a class or
> an inte
801 - 900 of 900 matches
Mail list logo
