work with the project running on
a docker container
Thanks in advance!
Carlos
Eclipse for C/C++ developers may work as well. I did use it for writing
an xdebug patch and reading the PHP source code.
Regards,
Pierre
XML_RPC-1.3.1.tar
Please do it. I cannot do it that soon.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ock solid and
portable solutions and keeps BC with all working applications.
This was what I said for months without too much success. This was even
our plan to add pecl/date as ext/date in 5.1 but Derick thought it is
better to go this way, so it goes...
--Pierre
--
PHP Internals - PHP Runtime D
ve in the PHP releases.
As a side note, you should ban STFU, whining, and other related words
from your vocabulary, at least in the next 20 years. They do not have
their places here, not the way and where you use them.
Regards,
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
listening the other
contributors.
And the question is more about delaying 5.1.0 or not. I doubt it is a
possible to delay again 5.1.0. There is thousands of critical fixes in
there, and many people are waiting for them since months. Sadly.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to fix them in a minor release is the best bad idea
of the year.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, 28 Sep 2005 15:02:38 +0200 (CEST)
[EMAIL PROTECTED] (Derick Rethans) wrote:
> I think that's a very marginal problem, perhaps a problem for 0.1% of
> the world population. I think we can live with that.
Is it the same 0.1% as in 5.0.5?
--
PHP Internals - PHP Runtime Development Mailin
e drop all the Derick's changes and restore the previous codes, I
doubt we have enough time to find a valid solution or implement any
fancy tags.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
do you mean E_STRICK compatible?
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ar
> does not seem to work at all with the .phar.
Forget to mention than the E_STRICT and is_a warnings have nothing to
do with the phar itself but the PEAR code itself.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Sat, 1 Oct 2005 16:48:47 +0200
[EMAIL PROTECTED] (Marcus Boerger) wrote:
> Hello Pierre,
>
> Saturday, October 1, 2005, 4:24:02 PM, you wrote:
>
> > On Sat, 1 Oct 2005 16:17:19 +0200 (CEST)
> > [EMAIL PROTECTED] (Derick Rethans) wrote:
>
>
> >> 1.
ble-pear. Seriously, we have to keep BC with php4.
We cannot maintain 2 branches of this app. A solution for php5 only
will come in time, and will be ready for php6 as well (from a UC point
of view).
So now I think it is time to stop shooting at pear and at Greg. Move on
nothing to see ;)
--Pierre
eaking "everything" out there.
I would like to go with a notice for the next stable release (both
5.0.x and 5.1.0) and see when we can make it as a fatal error,
something like 5.2 or so. HEAD can keep the error as it was.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To un
On Mon, 10 Oct 2005 20:29:32 +0200 (CEST)
[EMAIL PROTECTED] (Derick Rethans) wrote:
> On Mon, 10 Oct 2005, Stanislav Malyshev wrote:
>
> > IA>>It was MFHed to 5.1
> >
> > Why not to 5.0?
>
> 5.0 is dead? :)
5.1 is released? :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
rrelevant. You only hide the possible lack of
scalability behind hardware improvements.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
lback solution ?
> > Or even better - to download and install not compressed version of
> > the phar ? Or at least use --without-pear when there is no
> > --with-zlib or it's --with-zlib=shared ?
> >
> > Greg? Pierre? Any other ideas?
>
> I think we c
On Fri, 14 Oct 2005 01:39:08 +0400
[EMAIL PROTECTED] (Antony Dovgal) wrote:
> Also, what if someone uses --without-zlib? The installer would fail
> again?
Yes, so the solution is to go with uncompressed phar in php releases.
It gets compressed anyway.
--Pierre
--
PHP Internals - PHP R
On Thu, 13 Oct 2005 21:02:09 +0200
[EMAIL PROTECTED] (Oliver Grätz) wrote:
> Pierre schrieb:
>
> > This argument is irrelevant. You only hide the possible lack of
> > scalability behind hardware improvements.
>
> A "lack of scalability" will only occur if th
On Fri, 4 Nov 2005 03:28:57 -0800
[EMAIL PROTECTED] ("Fr_d_ric Minne") wrote:
> I have a pear account (username zefredz) and I request a cvs account
> and the permission to access and modify
>
> /peardoc
> /pear/Validate
>
> on the CVS
>
> thanks in a
ce
As I told you earlier, please use the _cvs account request_
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
losely typed, I see nothing wrong to pass an integer as string
there (for example, imagecreate("100", "100"); works).
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, 15 Nov 2005 09:17:20 -0800
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> Pierre wrote:
> > On Tue, 15 Nov 2005 18:59:32 +0200 (EET)
> > [EMAIL PROTECTED] (Jani Taskinen) wrote:
> >
> >> If you pass bad data to a function, it should not warn you?
> >
om a database
results, results can sometimes use fixed length strings.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
crappy (yes crappy) new date
object ON by default in 5.1.0.
We agreed to not active it by default but let it under the experimental
#ifdef so Derick can still be lazy and use the same tree to maintain
his stuff.
I ask to stop the realease process, put all this Object date back in
the experimental #
On Thu, 24 Nov 2005 21:52:28 -0500
[EMAIL PROTECTED] (Ilia Alshanetsky) wrote:
^
> Pierre first of all I put the change in after a discussion with Derick
> and a number of the while you were present btw. This was done to
> declare the date class for "future" proofing and allow
On Thu, 24 Nov 2005 21:23:17 -0800
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> Pierre, I agree with you that it was a bad idea to turn on the stub
> date class in the final release candidate giving people less than a
> week to notice that we now conflict with a common pear class. We
only period, who cares?
he commited and replace strtotime...
Then comes the replacement of date() and some other functions, and now
the addition of a date """object""".
Can we really say it is a mistake? a lack of attention from QA people?
from users? from PEAR? I do n
at this class is going to look like
> and how we transition pear/Date users. Naming it date_ex (for
> experimental) or something like that for now lets us keep the class
> constants as they are and hopefully Derick and Pierre can come to
> some sort of truce on the actual implementation.
in commit messages).
This release is a mistake and again you are responsible for that.
Assume your wrong decisions once.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ill have plenty of times to be warned or update
their codes.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
robations around this
list.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ld do it in an
> >>orderly manner and give people some time to migrate to something
> >>that actually makes sense.
> >>
> >>-Rasmus
>
> Right! And changing a class name from a PHP program takes just a few
> seconds..
Wrong, you have to first test, change a
re and the
consequences. Blaming non prefixed names, people having not tested the
last 2 RC or anybody else but this person is wrong, period.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
; any) 3) when namespaces become available, reserve "PHP" for all future
> internal classes
Reread the previous thread, this solution is not acceptable.
The only safe solution is to put it back in the #ifdef. We have then
time to do the right things and right names in php6.
--Pie
On Sat, 26 Nov 2005 00:50:04 -0600
[EMAIL PROTECTED] (Greg Beaver) wrote:
> Pierre, you can do all the #ifdefs you want, this idea does not
> prevent this :). In addition, the #ifdef has no effect on this idea.
You do not get the main problem.
- The ifdef makes it disappear from a user
trong objection 5.1.1 (5.1.0 + this patch and nothing
> else) goes out on Monday.
I have strong objection, as you know.
Rename it does not deserve the basic idea of a Date class. It does not
have to exist, period.
We can add it in time in php6 and do the required reflection and
communication a
On Sat, 26 Nov 2005 10:22:25 +0100
[EMAIL PROTECTED] (Sebastian Bergmann) wrote:
> Rasmus Lerdorf schrieb:
> > Pierre can come to some sort of truce on the actual implementation.
>
> At least there is code from Derick on the table. If Pierre needs as
> much time to show
On Sat, 26 Nov 2005 15:07:15 +0200 (EET)
[EMAIL PROTECTED] (Jani Taskinen) wrote:
> On Sat, 26 Nov 2005, Pierre Joye wrote:
>
> > This ext/date problem is something I will hate to see happen again.
>
> Well, it's totally your own fault. I remember the couple of time
any time
> in the future it is introduced as "Date" will conflict with all
> existing code that has a class named "Date".
Yes, anytime in the future but _not_ in 5.x and not in a RC phase, end
of the topic for me.
--Pierre
--
PHP Internals - PHP Runtime Development
On Sun, 27 Nov 2005 22:55:08 +0100
[EMAIL PROTECTED] (Edin Kadribasic) 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 with th
u
even try to report bugs? contact them? Anyway, this list is not a place
to discuss such problems.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, 30 Nov 2005 02:52:59 +0100
[EMAIL PROTECTED] (Marcus Boerger) wrote:
> Hello Sara,
>
> nice work, clean patch, good solution - thanks! what more can one
> say?
commit? :)
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:/
t this would be the first extension we
> bundle which isn't under the PHP license.
This is not a valid reason. But it is not a problem either, as I said,
we will change the license back to PHP License, as you finally fix the
little problems in the PHP License 3.01, thanks for that :)
Reg
On Thu, 1 Dec 2005 05:05:40 -0800
[EMAIL PROTECTED] ("Marcelo Santos Araujo") wrote:
> I will help on Validate_ptBR.
> I am in contact with Silvano.
> His CVS id is: silvano
Confirmed, pear account. I will set his karma once the account is
opened.
--Pierre
--
PHP Inte
ason to not allow BSD-like or
other similar license for the extensions. For example the bundled GD is
not under the PHP License, or is it already not considered as part of
the extension? What difference does that make?
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscri
On Mon, 5 Dec 2005 00:02:27 -0800
[EMAIL PROTECTED] ("Farid Sadudin") wrote:
> help maintain the on PEAR package
He will help to maintain Services_Pingback. I will give him the correct
karma once the account is opened.
--Pierre
--
PHP Internals - PHP Runtime Development Ma
hen...
It is already done since last week.
And I still do not have some good explanation about this new
requirement.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, 06 Dec 2005 10:53:37 -0800
[EMAIL PROTECTED] (Rasmus Lerdorf) wrote:
> Pierre wrote:
> > On Tue, 06 Dec 2005 09:03:16 +0100
> > [EMAIL PROTECTED] (Derick Rethans) wrote:
> >
> >>> * Introduce xmlwriter extension via a symlink from pecl into core
> >
lib64), you do
not have to use this option.
For example, on my amd64 box I have to use --with-libdir=/lib64
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, 14 Dec 2005 07:30:27 -0800
[EMAIL PROTECTED] ("Craig Constantine") wrote:
> As per Pierre and Arnaud, I'm requesting a CVS account. I will be the
> new maintainer of Pear package System_Command. Copies of Pierre's or
> Arnaud's email messages available u
p version will may
be available in PEAR. NTLM is what you are trying to achieve, or a part
of it. Single Sign On is another problem, and can be done with various
auth mechanisms. Are you implementing SSO as well? :)
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
AFAIK he already said he would
> be willing to take on the job.
To be honest I would like to have you as RM. You have the background
to take the right decisions and other can help when it comes to low
level technical or security issues.
>From a management, feedbacks or compromises ready poi
Hi Arnaud,
I replied in the bug report, please check it again :)
Thanks for your feedbacks,
--Pierre
On 9/29/07, Arnaud.lb <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Here is a patch to fix bug #42718:
>
> http://bugs.php.net/?id=42718&edit=1
>
> The "unsafe_raw&qu
Hi,
One important thing we forgot to discuss is to drop VS6 support fin
5.3 and finally move to VS2005.
It has a couple of side effects but it is a one time job and should
make our life easier on windows from 5.3 and up.
Comments?
Cheers,
--Pierre
--
PHP Internals - PHP Runtime Development
On 10/3/07, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Pierre,
>
> dropping all vc6 build files seems like a good idea to me.
Only Stan (or Dmitry?) was given them some love lately but the rest of
us use the jscript based build system :). So yes, we can remove them
to the list).
I would prefer Stan's patch to allow keyword to be used as
class/method/function name. At the very least (the patch has
unsolvable issues), I have to agree with Andi, we should just go with
"use" (codesearch returns less than 10 results :).
Cheers,
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi,
On 10/18/07, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-10-18 at 12:08 +0200, Pierre wrote:
> > I would prefer Stan's patch to allow keyword to be used as
> > class/method/function name. At the very least (the patch has
> > unsolvable issues
l require gcc 2.7.2.3 or libc
1.0.9? No, we don't.
Nobody said that we will stop providing vc6 builds, only that we have
been sitting on vc2005 or 2008 long enough, it is time now to make a
step forward and enjoy these new versions. I'm sure MS people will
also be very happy to give us a hand if we need it.
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
One word: transparency.
It is amazing how it helps to discuss things instead of acting like that.
--Pierre
On Nov 27, 2007 11:51 PM, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> > +^pdo-specs $CVSROOT/CVSROOT/loginfo.pl [EMAIL PROTECTED] $USER %{sVv}
>
> For consistency wi
That's the main problem here
and it is not the first time that such thing happens. It is what many
of us don't understand.
Regards,
--Pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
hat people need - people won't
> use PHP just to commend us for oh so good process. Process is important,
> but it's a *tool*, not the *goal*.
Asking prior to acting unilaterally is part of a process. Starting to
push CLA in the core of PHP without even asking is somethin
lates. But they are a pain to use as package
(like "import DB.* as myDB").
As far as I remember, PHP did not want such concepts of package. I
think it is pretty much what everyone is looking for, to supercede
include/require in php libraries/apps (not in templates) and to
fantastica
es with the PHP
licenses or the lack of CLA.
Don't try to solve a non problem or don't try to close the PHP
project, it is already hard enough to get in.
Thanks for your understanding and happy Christmas holidays,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals
h like "subscribe to the list and start contributing
> patches" as opposed to?
I think you know what I mean, take a look at the amount of complains
of people having hard times to contribute a patch or to get stuffs in.
ok, off to holidays now :)
--
Pierre
http://blog.thepimp.net | ht
On Dec 21, 2007 7:38 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Only thing needed for this is willingness to actually listen.
Listen the masses: NO, we don't want CLAs in php.net, period.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals
ses", it is amusing.
I don't know how much answers you need to finally accept a fact...
Don't be blind, you perfectly see all other opinions from other
developers.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Dec 22, 2007 8:37 PM, Alexey Chupahin <[EMAIL PROTECTED]> wrote:
> Patching libGD
Confirmed, he maintains the openvms build scripts.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://ww
7;t confuse users calling "standard"
> something that may not be present.
Yes, we have asked that many many times. the Standard Php Library
belongs to the core part of php. Even if I slightly disagree with its
name, some of its parts should even be pushed in zend/, see the
archives for a
gt;
> Please use php-general for that kind of question.
This question makes sense here and brings yet again the question why
such things are not available by default.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
(we gave a short list already). Can we at least always enabled by in
5.3 and be done with it? It is annoying to have setups without it.
Happy new year! :-)
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Jan 1, 2008 6:02 PM, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On Mon, 2007-12-31 at 22:45 +0100, Marcus Boerger wrote:
> > Hello Johannes,
> >
> > I agree with Pierre here. How about finally making SPL built in
> > always
> >
about reducing the WTF
in some cases, especially when you have to work in teams with
developers not aware of PHP's "weirdness" (please don't tell me to ask
them to RTFM, that's off base).
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Check google for all fatal errors we introduced about OO strictness
(or getter/setter) and you will see what does that mean to be unclear
about how strict one should be.
I'm not arguing to force strictness but I would love to have it, on a
per class basis for example ().
--
Pierre
htt
On Jan 4, 2008 5:53 PM, Pierre <[EMAIL PROTECTED]> wrote:
> On Jan 4, 2008 4:52 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote:
>
> > But I *don't* want my functions to take an argument of arbitrary type -
> > it is in fact you who are missing the point. A type hi
ith all associated magical pains and useless tests), you
can do it. That's not the case for use who likes to use stronger
arguments (and we are talking about arguments only here).
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mai
On Jan 4, 2008 6:20 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Pierre,
>
> we never accepted this as a pro argument. Infact we often saw the
> necessaity to highlight something is optional to vote against it. We do this
> for a reason. That is we only want
On Jan 4, 2008 6:01 PM, Sam Barrow <[EMAIL PROTECTED]> wrote:
>
> On Fri, 2008-01-04 at 17:53 +0100, Pierre wrote:
> > On Jan 4, 2008 5:53 PM, Pierre <[EMAIL PROTECTED]> wrote:
> > > On Jan 4, 2008 4:52 PM, Gregory Beaver <[EMAIL PROTECTED]> wrote:
> >
standardized output
> > exists.
>
> Object serialization is very standardized, it has proper handlers, etc.
> As for outputting arrays, indeed, 'Array' is not very meaningful, but
> would "Incompatible type is call in function foo() /foo/bar.php line
> 123" be
e
OO strictness (with or without good reasons :).
About performance, I doubt there is any difference. The cast is done
at some point anyway. And the function/method will not have to add
these horrible tests like is_int, is_numeric and all other related
tests.
--
Pierre
http://blog.thepimp.net | ht
t;11an" returns 0 but raises an
error. I can live with "[0-1.]" being converted to integer or float as
it is the case now. Even I would rather prefer a strict hinting and
let the user of a method or function do the cast (for the reasons
explained numerous times in this thread).
--
On Jan 6, 2008 9:55 PM, Stefan Priebsch <[EMAIL PROTECTED]> wrote:
> Pierre schrieb:
> > When a method or function uses the strict typing, it is on purpose. It
> > is documented (self documented and hopefully using normal docs). There
> > is no need of error handlin
On Jan 6, 2008 10:48 PM, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> Hello Pierre,
>
> I agree something that is not really a number should not be converted into
> a number as it is not compatible but then...what do we do right now?
>
> [EMAIL PROTECTED] PHP_5_3]$ ph
a bad usage. That was the moto for the
strictness in OO and its fatal errors. But It will be possible as it
seems that we are going down the E_RECOVERABLE error, but that does
not make it a good thing.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime De
On Jan 6, 2008 11:15 PM, Stefan Priebsch <[EMAIL PROTECTED]> wrote:
> Pierre schrieb:
> > I don't see the point to make a application working when you pass to
> > it the wrong data, it is a bad usage. That was the moto for the
>
> So how are you going to deal wi
On Jan 7, 2008 12:01 AM, Stefan Priebsch <[EMAIL PROTECTED]> wrote:
> Pierre schrieb:
> > That what happens now with the numerous fatal errors. That's not the
> > case with an E_RECOVERABLE error. PHP has no compiler and all errors
> > will be see at runtime,
e conservative and reluctant to update their
systems. The worst is that they even follow blindly your choices.
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
3];
> $b = ['foo' => 'orange', 'bar' => 'apple', 'baz' => 'lemon'];
I like this one, +1
ps: no need to argue why you don't like, it would be nice to simply
say +1/-1, trolls quota is already full for this year :)
--
large projects too.
>
> Please look to code of ExtJS JavaScript Library - this syntax native in
> javascript and it very usable
>
> (excuse me for my English)
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
+1 (for the record in this thread :)
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
7;m however in favour to give a voice to our users.
They are the ones using our softwares...
Cheers,
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Jan 11, 2008 6:37 PM, Pierre <[EMAIL PROTECTED]> wrote:
> On Jan 11, 2008 4:47 PM, Johannes Schlüter <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I did a short count of the "votes" about the Array Syntax shortcut on
> > the list. I hope I&#
right to vote to php-src only
is respectless for all the documentation people.
And we can wait at least a week or so before closing the poll.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
have provided patches or not is irrelevant /for me/.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
0, +1.0], [-2.0,
0.0 , +2.0], [-1.0, 0.0, +1.0]] and I will use this new syntax only
with such cases like this one :)
(variables in string are nice, when used with moderation/caution)
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ler, effective and right manner (and not
discutable, ideally).
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
know perfectly the
portion of the PHP sources to take a wise decision or choise.
It is also a process to use when we fail to find a compromise. I still
strongly believe in our self discipline and control.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runti
important paragraph. As a convenience, I will paste here
again:
> It is also a process to use when we fail to find a compromise. I still
> strongly believe in our self discipline and control.
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Jan 17, 2008 3:36 AM, Mário Soares <[EMAIL PROTECTED]> wrote:
> I posted in the pecl-dev malling list, the intention of publishing a new php
> extension. And Pierre suggested to make it available in the php.net cvs.
Confirmed, he is talking about a wxWidget binding fo
On Jan 21, 2008 2:24 PM, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
> > Any objections to this?
>
> No. +1 from me.
+1
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Jan 21, 2008 3:38 PM, Antony Dovgal <[EMAIL PROTECTED]> wrote:
>
> 6 reasons why we must to get rid of The Switch ASAP
I was +1 months ago, I'm still +1 now :)
--
Pierre
http://blog.thepimp.net | http://www.libgd.org
--
PHP Internals - PHP Runtime Development Mailing Li
1 - 100 of 4331 matches
Mail list logo
