VCS Account Rejected: railto rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: fabpianista rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: lakshmanphp rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
eaked stacktrace, no leaked credentials, user is informed, everyone
is happy :-)
Yup everyone should do that.
I personally like Tracy from Nette which has a production mode that will
show a nice error page: https://tracy.nette.org/en/guide
Perhaps PHP should display a page like that instead of a
nd an
email to you when there is an error:
https://stackoverflow.com/questions/277224/how-do-i-catch-a-php-fatal-error
We used that solution for quite some time, but it can quickly overload
your email server when you have millions of requests producing errors ;)
--
PHP Internals - PHP Ru
VCS Account Approved: marandall approved by kalle \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: villfa approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi all,
I am working on this PR: https://github.com/php/php-src/pull/4797
It implements the ability to set a userland callback function that would
allow or deny SQL queries in SQLite using its internal authorizer logic.
This is a native feature of SQLite that is currently missing from the
VCS Account Approved: kocsismate approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: alditis rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: dmarinov rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: schemer rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: vishnu rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: strongholdmedia approved by rasmus \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: dasl approved by rasmus \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: noobshow rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: dual rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: dreboard rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: bariseser rejected by rasmus /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: dalehirt approved by rasmus \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: nicolasgrekas rejected by salathe /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: nicolasgrekas approved by pajoye \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: alexdowad approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: theodorejb approved by derick \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Approved: ilutov approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Rejected: nusphere rejected by kalle /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Rejected: gandung rejected by kalle /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Rejected: ondrejmirtes rejected by kalle /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Rejected: kaiili rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Rejected: just-test rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Rejected: just-test2 rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Approved: adambaratz approved by tyrael \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
o port
this to PHP7.
Thanks,
--
- php-...@coydogsoftware.netdiff --git a/ext/opcache/ZendAccelerator.c b/ext/opcache/ZendAccelerator.c
index 985a4ef..3522861 100644
--- a/ext/opcache/ZendAccelerator.c
+++ b/ext/opcache/ZendAccelerator.c
@@ -52,6 +52,8 @@
typedef int uid_t;
typedef int gid_t;
cknowledged in the bugtracker and
in old php-internals posts, but I've seen nobody from the PHP Project
explicitly acknowledge the permissions bypass vulnerability. If my
meaning isn't clear I can provide proof of concept off-list. The
permissions bypass affects both apache2handler (eve
Hello Dmitry,
A quick question after considering your comments and doing a bit more
homework on extension lifetime:
On Thu, Nov 10, 2016 at 08:10:19AM -0600, php-...@coydogsoftware.net wrote:
>
> On Thu, Nov 10, 2016 at 08:51:58AM +, Dmitry Stogov wrote:
> >
> > Th
Dmitry,
Thank you for taking the time to answer my questions. Time allowing,
I'll be taking a closer look at the code this weekend. I do have a
couple of quick comments, see below:
On Fri, Nov 11, 2016 at 07:31:03AM +, Dmitry Stogov wrote:
> On Nov 10, 2016 5:10
VCS Account Approved: sven approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Approved: emir approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: bof rejected by kalle /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: mprelude rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: pakistanimoon rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: markbaker rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: rakeshkush87 rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: fp rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: alonsorivel rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VCS Account Rejected: cranavvo rejected by cmb /o\
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
more about
the more poignant issue of the current pace of deprecations in PHP, the
impact of the workload these cause for open source project maintainers
and the stagnation I'm currently seeing in PHP open source releases and
innovation as a result of this.
As I'm posting here now anywa
VCS Account Approved: timwolla approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
bly won't be completely arbitrary.
It might be coming from a discovery process that reads yml files or
annotations, or that calls some kind of hook in php. Or it is
generated with string concatenation.
Whatever it is, it is probably explicitly or implicitly hard-coded somewhere.
Here is
VCS Account Approved: aaronjunker approved by cmb \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Approved: devnexen approved by derick \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
VCS Account Approved: nielsdos approved by derick \o/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
is should throw an error, this feature makes sense as '::' is
always for accessing static stuff, it is quite logic in the end:
:: for static (constants, static variables, static methods)
-> for the rest
I think this feature is documented somewhere in the doc, that's where
Hi people of the PHP world,
I just have proposed a patch to have SQLite3 open_blob feature
implemented in PDO_SQLite: https://github.com/php/php-src/pull/2698
This follows my patch to implement this feature in the SQLite3 extension
a few months ago.
Now my aim is to implement missing
akes it so that the methods are not accessible until the connection
has been established, which is a weird behaviour imho).
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
a better idea than driver-specific methods and I don't know enough
C/have enough time to do anything else, so I won't submit any
proposition that I won't be able to do myself.
Cheers.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
work with. It is not
helpful: it's just more tech debt dumped on millions of consumers.
I care because I need those features in my projects, and I'm not the
only one.
But if those late-loading methods don't suit you, what do you propose
instead?
--
PHP Internals - PHP Runtime Deve
;t see how that would be possible.
My feeling is that it would have been better to have a class extending
PDO for each driver, adding additional constants and methods, but that's
not how PDO has been designed, and I'm not gonna suggest that we should
rewrite PDO now.
And yes, you a
Kia ora,
I'm requesting access to wiki to be able to write the RFC on
implementing missing pdo_sqlite features, following pull request
https://github.com/php/php-src/pull/2698 and discussion on this list.
My account on the wiki is "bohwaz".
Cheers.
--
PHP Internal
Hello, anyone? :)
Kia ora,
I'm requesting access to wiki to be able to write the RFC on
implementing missing pdo_sqlite features, following pull request
https://github.com/php/php-src/pull/2698 and discussion on this list.
My account on the wiki is "bohwaz".
Cheers.
--
PHP
o
Discussion should happen in the next two weeks before going to vote.
The actual patch is here: https://github.com/php/php-src/pull/2698
Suggestions and discussions welcome.
Cheers.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
different here, and openBlob allows
stuff that PDO::PARAM_LOB with bindColumn and bindParam cannot allow
currently. In conclusion openBlob is still useful as it allows accessing
a BLOB outside of a statement and allows to read and write at the same
time without having to load the blob in m
On 02/10/17 01:48, BohwaZ/PHP wrote:
So for me the use case is quite different here, and openBlob allows
stuff that PDO::PARAM_LOB with bindColumn and bindParam cannot allow
currently. In conclusion openBlob is still useful as it allows
accessing
a BLOB outside of a statement and allows to
at, and it's not the subject of this RFC :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
on it.
This is not how I understand the documentation:
"PDO::PARAM_LOB tells PDO to map the data as a stream, so that you can
manipulate it using the PHP Streams API."
But this seems to be quite chaotic, reading
https://secure.php.net/manual/en/pdostatement.bindcolumn.php
"Sin
o the discussion so far :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
t/rfc/implement_sqlite_openblob_in_pdo
Vote will end on Wednesday the 25th of October.
Thanks to everyone who contributed to the discussion so far :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Le 12/10/2017 12:00, Dan Ackroyd a écrit :
On 11 October 2017 at 22:03, BohwaZ/PHP wrote:
Hey,
For people voting against the RFC, could you please explain your vote
here
so that we might understand?
Cheers.
I think people were reasonably clear during the discussion.
Having certain
Le 04/02/2019 01:14, azjezz a écrit :
In my opinion, current design looks old, outdated and bland. This
sadly may reflect "badly" on the language reputation nowadays.
I find that the main PHP website is quite good actually, the design
looks modern, it is quite clear and easy to
nd of weird :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
gt; I always thought constants were about imposing an
> unchanging nature to
> the data and not about visual aesthetics when
> reading code :/ I too
> would like to see constant support of non-scalar
> values.
Same here. I have a number of static arrays that I use
for reference dat
t;ugly" syntax). Personally I
> don't see anything
> ugly or wrong with using the above syntax.
>
> Cheers,
> Rob.
Agreed. "ugly" is a subjective argument and does not
change the usefulness of that particular ability.
Where would the C language be without the ability to
define arbitrary constant values?
- Gabriel
=
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ess,
which is only used for sending and receiving mail from
the list. Pretty annoying for someone who doesn't use
their products. Thankfully I can just whip up a new
address and resubscribe, but I figured I'd let you
folks know in case you're receiving the same crap.
- Gabriel
=====
Is it expected that call_user_function() will free up
memory allocated to the function name and argument array?
=
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Is it possible to intercept a function call (user
space or built-in) in the Zend Engine and execute user
space code before/after the function call?
=
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
fter the function call?
> >>
> > Yes, you can do this by way of a Zend extension
> (not a PHP extension
> > mind
> > you).
> >
> > The parts of Zend/zend_extensions.h you'll want to
> pay attention to
> > are:
>
> You can also do this b
I found the book Advanced PHP Programming to be quite
helpful when I started working on the zeroconf
extension. There's a number of chapters dealing with
extensions and Zend engine internals.
--- Chris Cranford <[EMAIL PROTECTED]>
wrote:
> I'm trying to create my first module
descriptions, etc. - or
>
> This would not require anything but basic knowledge of PHP and lots of
> time. If somebody wants to do it, arguably millions of people would
> benefit from it - since it would make real bus more prominent, thus
> making PHP devs more likely to fix them, thus
at ES 3.0 (Intel)
PHP Version: 5.0.0RC3
New Comment:
It works with the Zend Optimizer/Debugger, so it's not our problem.
You should report the problem to Zend.
Previous Comments:
[2004-07-20 17:10:47] jason at ionzo
Hello, please discuss about error collecting implementation in next PHP
releases
Exceptions have common differences that restrict using them to collect
errors
1. Timeloss (trace collection) on call new() on any class that implements
\Throwable
2. To collect errors and return it to the upper level
rs could be collected as a stack on
language level. Directly in place you need that stack instead of
everywhere. Also forcing to close applications is safe-shield, instead of
validation errors that could be found anywhere. PHP devs in most even
imagined a solution that "you have to do validati
ecial
decorator or additional command could initiate the raise collector right in
the function !
You collect only the cases you want to collect. That's the difference.
вт, 6 февр. 2024 г. в 18:20, Alexander Pravdin :
> On Wed, Feb 7, 2024 at 12:00 AM Григорий Senior PHP / Разработчик Web
> &l
se global error bag stack that you can enable or
disable for your needs outside function ("in controller", GRASP) or inside
function directly like old good times $errors[] and if ($errors) { return
null; }
вт, 6 февр. 2024 г. в 18:23, Alex Wells :
> On Tue, Feb 6, 2024 at 3:58 PM
is just a bad idea. People will shove megabytes of logs
> into it in a loop and them file reports "why is php using 2 GB of RAM?" -
> this is literally a daily question you get woth relation to Doctrine when
> people try to run bulk operations, do not disable trace logger and them
and that while (true) and then/catch should be
different patterns.
вт, 6 февр. 2024 г. в 19:08, Григорий Senior PHP / Разработчик Web <
6562...@gmail.com>:
> My function seems like this:
>
> ```
> _error_bag_error(error) {
> if (stack.errorBag) {
> stack.errorBag.add(er
from within - once you
integrate a really bad external system with its own checks, which are
described in hundreds of documents, I'm sure you'll encounter new bugs once
the "working" code is released to production. And then you will need to
quickly and easily reorganize i
Thanks for suggestion about assert() use cases, i know it exists before,
but never used.
Usually if something shouldn't happen i throw exception there, or at least
type control. Its like manual mark for the future - you doing something
wrong, fix it.
Error collection case its about "you're right,
ction itself won't change existing code then, it works like
an observer pattern now.
ср, 7 февр. 2024 г. в 13:21, Robert Landers :
> On Tue, Feb 6, 2024 at 9:22 PM Larry Garfield
> wrote:
> >
> > On Tue, Feb 6, 2024, at 7:56 PM, Григорий Senior PHP / Разработчик Web
> wr
Analyzing the problem on a single level operation is incorrect. New code
and simple operations are fully covered with exception/try/catch flow.
The main point i tried to attract your attention is that if you working in
batches/queues/pipelines you still need errors collection, and if you made
erro
All other cases should be covered without exceptions. If you use
exceptions on any occurred error as "truth way" you will meet risk and also
timeloss on any misformatted batches/user-inputs.
ср, 7 февр. 2024 г. в 18:06, Григорий Senior PHP / Разработчик Web <
6562...@gmail.com>:
I still don't understand why the problem is signature and moving a simple
throw statement to return type, and then rewriting the catch statement to
oneline-r.
I am completely satisfied with the php way of working with method
signatures except non-critical cases:
- still no `undefined` typ
JIT I've had this solved, not only the application, but a way to.
Am sharing my experience without labels "bad", "cood", "truth" or
"correct", like you did.
Your arguments are based on your principles and I don't see in your words
any point to discuss, so - use pm or share here secret of error-fr
Ok, I understand your position. Want explanations about personal behavior -
please write by telegram.
PHPStan is out the case.
SOLID is not a marker of good architecture, it's a marker of idealistic
understanding, for me.
I already long ago passed that time where I can just say "this code is bad
Just because PHPStan is a ready solution for design errors that you can
predict.
My case is about errors that you detect later, after the design is
finished, PHPStan shows you that "all done!".
Because it's not \LogicExceptions (types, mappings), it's all
\RuntimeExceptions... You have to implemen
times on the Earth - firing out developers who
"know the truth", hiring cheap developers who "just do".
You could believe in correctness or help people who need that help.
I understand that php spent many years on fast solutions, and btw, I am
glad to write code with PHP, even wit
1. Do some benchmark with
```
> I've worked on PHP (and non-PHP) applications with (tens of) millions of
lines of code
Grats, you're a hero. Now, you're a hero.
You can solve the application in your paper notebook. That does not explain
why computers should know some correctness and not help you, because
Working with remote servers is a little bit harder than just catching the
exception.
Just implement OOP stuff gives no benefit except "do not read the docs, but
use IDE". Usually count of curl options is so big that it wont help.
And also, there's multicurl too.
There's batch calling with limit t
function to "task"
available to call it later somewhere, maybe in another promise
```
Why is the PHP implementation redesigned from scratch instead of using the
idea of the one that works?
ps. Guess, the discussion to change syntax that you cold rewrite with
single line:
```
// >
101 - 199 of 199 matches
Mail list logo
