asses differently just because PHP can't deal with it. It may not be
trivial to fix, but to the end-developer, it's a trivial problem and it's
something that should just work.
Dan
On Thu, Nov 6, 2008 at 3:54 AM, Larry Garfield <[EMAIL PROTECTED]>wrote:
> On Wednesday 05
uffix
the class name with 'Helper' to reconfirm that, just because the PHP engine
doesn't like it.
Dan
On Thu, Nov 6, 2008 at 9:50 AM, troels knak-nielsen <[EMAIL PROTECTED]>wrote:
> On Thu, Nov 6, 2008 at 10:35 AM, Dan <[EMAIL PROTECTED]> wrote:
> > What if
upport the basics in a way that
make sense.
Dan
On Thu, Nov 6, 2008 at 12:03 PM, Steph Fox <[EMAIL PROTECTED]> wrote:
> In .NET, I can stick an Array class into my own namespace, extending the
>> System.Array type if I want to and use it in my code without issue. Why
>> can
>
Why can
I not do that here? Is it simply that you're so worried about backwards
compatibility that you feel that you can't make the necessary changes to the
language to implement something fully?
Dan
On Thu, Nov 6, 2008 at 11:43 AM, Ben Davies <[EMAIL PROTECTED]> wrote:
> &
>
> You're assumption is wrong then, NULL isn't treated as not passing a
> value. The reason it worked with substr was by pure chance.
>
Out of interest, is there a reason that that is the case? Surely passing
null would be best treated as the same as passing nothing?
method.
function bar(A $a){
$a->foo();
}
function foo(){...}
}
But I agree, the number of times I've wanted to do this is low.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
s, so I hope
that we can get the implementation right, but this RFC isn't it.
cheers
Dan
On 5 February 2015 at 20:14, Andrea Faulds wrote:
> Good evening,
>
> At long last, I’m going to put the RFC to a vote. It’s been long enough - I
> don’t think there needs to be, or will be,
search for
the things that needed fixing.
You could then put links to the PR from checklist for an example of
the change in place.
cheers
Dan
An incomplete checklist for migrating an extension to PHP7
--
1) Parse paramet
software can have bugs. Who knew! Seriously though, there
was a bug displaying the phpinfo page caused by the migration to the
7, but it's fixed now. If you're still having issues, please open an
issue in the link above.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing
ments.
Claiming that only things that have near unanimous consensus can be
moved forward is bogus.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 17 February 2015 at 00:22, Nikita Popov wrote:
>
> Thank you for taking over.
>
> I like "use strict" and "declare as top-level only" most.
That would be this no vote changed to a yes.
And I'd also like to say thank you Sara for taking over.
cheers
handleException($ee);
}
catch(Exception $e) {
handleException($e);
}
As that would be the only place it would be required to catch both types.
TL:DR EngineException needs to not extend Exception, whether we need a
super class is not as clear.
cheers
Dan
--
PHP Internals - PHP Runtime
e
> would require more changes and will make more BC breaks.
Please can you explain what those problems are?
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
design decision.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ion currently will still behave as it
does before. The only change to the Exception class would be add the
interface to it's declaration. I can't see how this causes a BC break.
Please can you say what the BC break is if you think there is one.
cheers
Dan
--
PHP Internals - PHP R
Doctrine/ORM/Query/Expr.php#L443
I don't think changing the language in a way that breaks Doctrine
would be feasible.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
>config['jab_host']) ||
empty($this->config['jab_username']) ||
empty($this->config['jab_password']) ||
!@extension_loaded('xml')
);
Seriously, a double-negative at the end of a five piece statement that
combines falsy things? Making it eas
>From the RFC:
> Patches and Tests
> Will be prepared before vote.
The implementation details may determine how some people vote. Is the
patch still coming before the voting is opened?
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://ww
n/2011/05/13/php-code-injection-a-simple-virus-written-in-php-and-carried-in-a-jpeg-image/
As soon as you have any possibility of including a file uploaded by an
attacker, you are probably going to lose.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe,
orrect
type. And so type coercion is at best unneeded, and usually not
wanted.
I can understand why people might only want to use weak types for
their code base, but for you to continually dismiss people's desire
for strict types after all this has been explained to you multiple
times is ver
&m=142150339323854&w=2
As this RFC targets PHP 7, I plan to open the voting before the cut-off date.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
The same behaviour can seen with the code below.
cheers
Dan
class Foo {
private static $internalConstruction = false;
public function __construct() {
$constructionAllowed = !self::$internalConstruction;
self::$internalConstruction = false;
if (
eneral discussion about error handling, it
is specifically about the behaviour of internal classes being
'special' either by having behaviour which is not possible for
userland classes to do, or just being unusable after being
instantiated due to incorrect parameters.
cheers
Dan
--
PH
ion is happening.
Having an intermediate step of E_DEPRECATED notice would not affect
the amount of code that they would need to change nor will it make it
significantly easier to detect places in their code where this
behaviour is occurring.
cheers
Dan
--
PHP Internals - PHP Runtime Development
esn't
make it significantly easier to do.
So even though I hope we can clean up the exception hierarchy, merging
the engine exceptions is the right choice imo.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
e code that will work on 5.x, 7 and 7.x by just not using scalar
type hints.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
g "\" or without."
- With a trailing "\"
- Without a trailing "\"
This would have allowed all voters to express their intent for both
parts of the question, without being forced to vote 'yes' if they want
a say in the exact syntax used.
cheers
Dan
Ack
-
t at the same time that some of the problems will be left for five
years show that this isn't a sensible RFC to vote for, even for the
people who just want weak types
cheers
Dan
.
On 11 March 2015 at 15:10, Zeev Suraski wrote:
> The vote on the Coercive Scalar Type Hints is now open for v
rland.
The size of the PHP core codebase is already unwieldy. I think any
suggested addition needs to have a clear advantage over being
implemented in userland
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
e of 67108864
bytes exhausted
i.e. 95% of memory allocated isn't being used and could be freed, but
hasn't because the number of GC objects didn't reach 10,000 and so the
gc_collect_cycles didn't kick in automatically.
cheers
Dan
http://www.php.net/unsub.php
Patrick Schaaf wrote:
> But that has proven, in the past, a fountain of joy wrt.
> placement, with variations needed for APC and opcache, and general frustration
> all around.
Is there a bug report for the problems? OPCache shouldn't have
side-effects on the code.
cheers
Dan
On
ng but not seeing anybody
> explaining.
Perhaps if you sent fewer emails to the internals list, people would
be more likely to read and respond to the emails you do send?
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
o justify
making decisions about the language at the last minute, particularly
as the last version of the RFC I read breaks a whole load of valid
code.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
known cost of adding
syntax to the language, as well as the unknown cost of blocking future
use of the 'in' keyword".
I'm sorry, but I just can't see that the value in adding this comes
anywhere close to justifying it's addition.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
g instance or throwing an exception, is the standard
behaviour we want in PHP.
cheers
Dan
Ack
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
icity. The scalar_type_hints_v5 is currently passing, and the
Coercive STH RFC is very, very unlikely to pass.
Please will you carry out your promise to retract the Coercive RFC and
support the other RFC a few days early, so that we can move forward
getting PHP 7 ready rather than having this c
this comes
anywhere close to justifying it's addition.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 16 March 2015 at 09:05, Xinchen Hui wrote:
> Hey:
> I don't like strict_types at all..
>
And you would never be forced to use them.
But you're voting against allowing anyone else to use them. :-(
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To
de that runs in strict mode, will automatically work in weak mode.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
so are
still able to run the current version.
As Marco said, even if it's possible to 'fix' the code that uses this
behaviour - it's a really really useful pattern in the rare case where
it's needed.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ically the warning is not given. i.e. the code below gives an
error 50% of the time. This is why people need time to evaluate code,
and why opening a vote straight after you've made a change to how the
syntax works is really bad idea.
This was built off your branch with commit
6ca9d912c9a
Thank you Zeev.
On 16 March 2015 at 14:35, Xinchen Hui wrote:
> Unecessary for everybody, one or two change from no to yes will make it pass.
> :)
Although not necessary, it would reduce the level of drama, which
would be a good thing.
cheers
Dan
--
PHP Internals - PHP Runtime Devel
as part of future improvements to PHP's type system.
Can anyone please make a strong argument for why 'resource' and
'mixed' should be reserved, if we currently have no plans to use them?
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
d.
I think having clearer rules about what lobbying is permitted, and
introducing some rules on who can vote on what would be a better way
of limiting the effect of lobbying.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
cceptable to change the behaviour in a minor version.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
evert the RFC, before
the cut off time for RFCs. This is one of the reasons why someone
editing the text of a passed RFC is utterly unacceptable.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ng able to dynamically generate code, as once you've
called `class_exists("SomeAutogeneratedClass", true);` you can no
longer use the registered autoloaders to load that class, and instead
have to load it by hand.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
that I may have missed a couple of classes. I'll
try to get those updated before you have a look.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
indicates
what the parameter is. The only place where you could argue this
syntax is needed is when you're passing in just a bare 'true' which
has no syntactic meaning associated with it.
That syntax works for all versions of PHP, so I guess a new syntax
that achieves the same thi
This was approved by a vote of 32 - 1.
Dmitry said that he would like to review and possibly polish the patch
before it is committed.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
>
> We could
> also consider going for ‘lax’ or ‘lenient’ as the opposite of ‘strict’,
> although I think we can easily do without introducing a new word into the
> vocabulary here.
>
>From an user perspective, I'd suggest that "lax" would potentially carry
more negative connotations than "weak."
#x27;semantically' meaningful i.e. it allows people to tell the cases
between the two types of errors apart.
It probably bears more thinking about though.
cheers
Dan
$formatInfoList = [
["en_US", "{0,number,integer} monkeys on {1,number,integer} trees
make {2,number}
tion _default_exception_handler(\BaseException $e) {
}
}
else {
function _default_exception_handler(\Exception $e) {
}
}
Yeah, this isn't the most awesome thing ever to have to do, but imo it
sure beats having to change code in the middle of applications.
cheers
Dan
--
PHP Internals
oint in the future? i.e. does it do
something that isn't supported by other libraries in PHP?
ii) If it's not possible (or desirable) to remove it, how could we
increase the warning level against using it?
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ignoring such global configuration else it's impossible to have a TS
> version of PHP
The global is held by the C libraries, not in PHP code. And yes, the
implication of that is that setlocale can not be thread safe.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ther than to make the warning larger on the manual page?
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Julien,
I am unsure of the timing windows for things being committed to being
in a release, but it seems unfortunate to not have this included:
https://github.com/php/php-src/commit/86f983bd3ea13def42e36842e03f785d02d40a7f
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
es, I think the preg_replace_callback_array addition probably
should have gone to a vote. I know some people have stated objections
about having too many RFCs - but I think that having a small hurdle to
adding stuff to core is not a bad thing. If nothing else, it forces
people to think and describe the
ad_safe_setlocale'
* If it's enabled the setlocale function calls the new thread safe
functionality.
* If it's disabled the setlocale function calls the current non-TS C
setlocale function.
Does anyone have a better suggestion on exposing a thread safe version?
cheers
Dan
--
P
the behaviour at
major/minor version, and if this was introduced then having to
`thread_safe_setlocale=off` for 7.1 and `thread_safe_setlocale=on` for
8 could be correct.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
g complexity to a language to try to work around
programmers ignoring exceptions is not a good idea.
I think the RFC needs to be clearer in the specification of the order
that static initialization is called in. e.g. class B extends class A.
Both A and B have static initialization blocks. When a use
On 14 April 2015 at 17:39, Johannes Ott wrote:
> Am 14.04.2015 um 16:33 schrieb Dan Ackroyd:
>
>> Here is some feedback then:
>>
Johannes Ott wrote:
> But in the new draft (v0.4) I'm preparing at the moment I'll try to
> formulate the trigger "first c
o change the setting in the version of PHP
that they provide. For the general release of PHP, unless someone can
demonstrate how it wouldn't be a security problem, continuing to
default to the current secure setting sounds sensible to me.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
T_MAX;
mydb_find_by_id($x+1);
Unless you're also suggesting replacing PHP's current maths operations...
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
k when people want to write unit/integration tests
to test the behaviour of a module when an EngineException is thrown?
If you can't create a certain type of exception, it would mean that
some code is basically untestable...which seems bad.
cheers
Dan
--
PHP Internals - PHP Runtime Develop
On 15 May 2015 at 17:12, Xinchen Hui wrote:
>> How would that work when people want to write unit/integration tests
>> to test the behaviour of a module when an EngineException is thrown?
>>
>> If you can't create a certain type of exception, it would mean that
>> some code is basically untestable
it running as a
long-running CLI process.
If nothing else, it would be nice to get the GC_BENCH benchmark stuff
working for the CLI again; it currently only works in certain
circumstances[2].
cheers
Dan
[1] <https://bugs.php.net/bug.php?id=41245>
[2] <https://bugs.php.net/bug.php?
On 16 May 2015 at 17:00, Ryan Pallas wrote:
> Why do you want to test parse exceptions? Lint your code before you run it
> and you won't have any. ... maybe I'm missing something
> obvious,
Yeah, there's been a misunderstanding. I'm not talking about wanting
to test whether my code generates par
ce must be either an instance
of Bar or Foo');
}
...
}
Re-using the built-in TypeException for this would be the right thing
to do and so it needs to be creatable in userland.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
on is also different the other EngineExceptions, as it's an
exception that people will want to throw from their own code instead
of having a separate UserLandTypeException.
Except for testing, people shouldn't be throwing ParseException or
other EngineExceptions from their code.
cheer
plication.
And a max memory_limit of 128MB where the application does the current
behaviour of falling over and dying.
I'll wait for some feedback, then write an RFC unless someone can say
something that would be significantly better, or why the above would
be either bad or technically unfeasible
On 19 May 2015 at 14:28, Rowan Collins wrote:
> Dan Ackroyd wrote on 19/05/2015 14:08:
>>
>> * When gc_collect_cycles is called (and potentially other functions),
>> at the end of that function check whether the amount of memory being
>> used is less than reset le
need to address
how much BC break it would cause, and why it would be worth it.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
uld need
to be cleaned up twice, which could be a large duplication of work and
BC break.
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
throw new TypeError("$newval is not a Foo");
}
parent::offsetSet($index, $newval);
}
}
cheers
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
s is another case where you are ignoring other people's use-cases,
and imagining that your use-case is the only valid use-case.
But the technical discussion is one that we should have when someone
is proposing this change - not when someone has committed it first and
then is asking for approva
ve been
discussed, but it looks like they won't be possible to implement in
time for 7.
Having function calls return bogus values without any warning is just
a very bad idea, and I don't think PHP 7 should ship with that
happening.
cheers
Dan
p.s. with the ini setting of pcre.jit=0 the code do
6, but providing a legacy
extension/compile time option, which would bring with it almost complete
backwards compatibility with PHP 5.
*Dan Cryer*
+Dan <https://plus.google.com/101400775372325517263>
@dancryer <http://www.twitter.com/dancryer>
On 17 July 2012 16:32, Andrew Faulds w
(for most of the required header files) +
Microsoft .NET SDK (for nmake).
However, my build is now dying because it can't find winres.h :(
Dan
On Wed, 30 Mar 2005 12:32:33 +0530, Arjun <[EMAIL PROTECTED]> wrote:
> [Sorry for blanket mailing.. Guess the list does not pass attachmen
On Wed, 30 Mar 2005 08:36:28 -0500, Dan Scott <[EMAIL PROTECTED]> wrote:
> Try grabbing the latest CVS version of PHP or the latest 5.0.x
> snapshots from http://snaps.php.net/ -- there were a number of patches
> since 5.0.3 that helped me get further on my attempt to compile on
Thanks Edin, grabbing your updated resolv.lib and dropping it into the
win32build directory got me over the last hurdle!
Dan
On Wed, 30 Mar 2005 19:20:11 +0200, Edin Kadribasic <[EMAIL PROTECTED]> wrote:
> You can download the lib from:
>
> http://ftp.emini.dk/pub/php/win32/de
uests the next result set from the database
*/
Thanks,
Dan
Note: somewhat confusingly, mysqli defines mysqli_next_result(), but
this is used to retrieve the results of a multi-query... a very
different thing, and not something I advocate adding to PDO. They
might have trouble disambiguating that fro
ion to the
manual. That's what I get for reading my own (incomplete)
documentation.
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
from the site will be invalid in
gc_maxlifetime).
So what you want are cookies?
---<
Dan Kalowsky"I thought you died alone,
http://www.deadmime.org/~danka long long time ago."
[EMAIL PROTECTED]-
On 4/28/05, Greg Donald <[EMAIL PROTECTED]> wrote:
> On 4/28/05, Dan Scott <[EMAIL PROTECTED]> wrote:
> > Does the segfault only occur when you load PDO into mod_php?
> >
> > If you haven't already tried it, try using PHP CLI to reproduce the
> > prob
On 4/29/05, Greg Donald <[EMAIL PROTECTED]> wrote:
> On 4/28/05, Dan Scott <[EMAIL PROTECTED]> wrote:
> > So three things:
> > 1. If you print the results of get_loaded_extensions(), you'll see
> > that pdo turns up as 'PDO', but you're looking
Make sure you read the "PHP and Unicode: A Love at Fifth Sight"
presentation available from http://www.gravitonic.com/talks/ from the
May 2005 -- Andrei and Derick have been working towards this already.
On 6/3/05, Steven Wittens <[EMAIL PROTECTED]> wrote:
> Hi,
>
> As a PHP user I'm sadly confro
e the default in php.ini-recommended, with E_ALL
| E_STRICT a documented (but commented) option.
Dan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 6/16/05, Zeev Suraski <[EMAIL PROTECTED]> wrote:
> At 20:39 16/06/2005, Dan Scott wrote:
> >On 6/16/05, Zeev Suraski <[EMAIL PROTECTED]> wrote:
> > > Why would you enable it then? You have to very explicitly enable it, as
> > > it's off by default, a
Try http://snaps.php.net/ for the "PECL extensions for the Stable 5.0 branch".
Dan.
On 7/6/05, Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Where do you get php_pgsql.dll for the PHP for windows 5.0.4 installer?
>
> I installed the PECL package - no pgsql.
>
Of course -- the "Collection of PECL modules for PHP 5.0.4" from
http://php.net/downloads.php. I had leapt to the (probably false)
conclusion that Christopher wanted a newer version of the module.
Dan
On 7/7/05, Edin Kadribasic <[EMAIL PROTECTED]> wrote:
> Just download regu
getting munmap'ed before libgcc_s. (libdb2 is
compiled from C++, thus the dependency on libstdc++.)
Based on past experiences with FreeBSD 4.6, Andrei and Rasmus
suggested that the problem may be a defective linker, which seems
entirely plausible. I'll try compiling PDO + PDO_ODBC (ibm-db
which PHP branches you can download, say php_oci8.dll PECL
> extension, point your browser at
> http://pecl4win.php.net/ext.php/php_oci8.dll
>
> Edin
>
Edin:
Thanks for all of your hard work on the Windows builds for PHP. As
impressive as your previous efforts have been (and they hav
the extensions
themselves (that, or we've managed to make a mistake in ibm_db2 that
matches an ext/odbc mistake).
Dan
On 9/24/05, Wez Furlong <[EMAIL PROTECTED]> wrote:
> Curious; I haven't updated glibc or libstdc++ on my system, and I
> didn't get this problem a few
27;s not a
major task, most of the content is contained here:
http://www.php.net/manual/en/install.pecl.downloads.php -- but there
will be a lag before the translations occur and the updated manual is
published.
Dan
On 11/25/05, Romain Bourdon <[EMAIL PROTECTED]> wrote:
> Ilia Alshanetsky a
tation, if
this is indeed the intention for taint mode, would therefore be
irrelevant.
http://devzone.zend.com/node/view/id/1526#Heading3 suggests that we've
had this discussion before and almost came to agreement that taint
mode would be used as a development tool.
--
Dan Scott
Laurentian University
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
forge.mysql.com/wiki/MySQL_Contributor_License_Agreement. Maybe
they're the ones pushing for a CLA this time around.
--
Dan Scott
Laurentian University
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
nother entity, they waive any right to reuse their own work in a
different forum - except under the terms under which that work is
licensed by the entity that now has the copyright for that material.
So an author can and should maintain copyright over the material they
contribute, but they contribute it under a license that specifies the
terms under which that material can be used (the PHP License, for this
project) by others.
--
Dan Scott
Laurentian University
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Thanks for the new SplDoublyLinkedList class - I'm looking forward to taking
it out for a spin.
Here's a patch for a few minor typos in the method docs:
http://scratchpad.coffeecode.net/proto_typos.diff
Dan Scott
http://php.net/manual/en/function.pdostatement-rowcount.php is what
you want, in that case. No reason to use PDO::exec() just to get the
number of affected rows.
Dan
On 12/22/05, Marian Kostadinov <[EMAIL PROTECTED]> wrote:
> Sorry,
> I don't remember:(
> The text was somet
1 - 100 of 754 matches
Mail list logo
