Regarding the mixed type-hint RFC:
https://wiki.php.net/rfc/mixed-typehint
> When no native type is present, it is unclear what type is expected
Regarding variance - in the examples shown in the RFC, it is still unclear
whether your intention was variance, or if you just omitted the type-hint
by
Am Do., 7. Feb. 2019, 10:27 hat BohwaZ/PHP geschrieben:
> 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
Hi Zeev,
On Thu, Feb 7, 2019, 4:55 PM Zeev Suraski All,
>
> I've read the detailed and very informative feedback from both Pierre and
> Dan, as well as feedback from others (Nikita & more) over the last few
> days, and I'm now convinced that breaking the Voting part away from the
> Workflow part
> On Feb 7, 2019, at 11:47, Vladyslav Startsev
> wrote:
>
> Hello everyone!
>
> Recently I noticed that there are strange behavior going on if I use
> bcmath functions (some examples you can see here
> https://3v4l.org/D3s7J). I also previously had little discussion with
> Sara Golemon on twitt
On Thu, 7 Feb 2019 at 18:01, Peter Kokot wrote:
>
> Hello,
>
> On Thu, 7 Feb 2019, 16:52 Christoph M. Becker >
>> On 07.02.2019 at 16:14, Sjon Hortensius wrote:
>>
>> > On Wed, Feb 6, 2019 at 4:14 PM Ben Ramsey wrote:
>> >
>> >>> On Feb 6, 2019, at 01:22, Peter Kokot wrote:
>> >>> I can help sor
Hello everyone!
Recently I noticed that there are strange behavior going on if I use
bcmath functions (some examples you can see here
https://3v4l.org/D3s7J). I also previously had little discussion with
Sara Golemon on twitter about this
(https://twitter.com/SaraMG/status/1087902930110480384). So
Hello,
On Thu, 7 Feb 2019, 16:52 Christoph M. Becker On 07.02.2019 at 16:14, Sjon Hortensius wrote:
>
> > On Wed, Feb 6, 2019 at 4:14 PM Ben Ramsey wrote:
> >
> >>> On Feb 6, 2019, at 01:22, Peter Kokot wrote:
> >>> I can help sort this mess. A separate fork out of the php/php-src was
> >>> not
Hello Bohwaz,
i think you should take a look at the mock ups[1].
I don't plan on using an JS Framework, the frameworks i suggested are
lightweight CSS Frameworks.
I'm also planning on keeping the shortcut redirects and maybe even improve them.
[1]: https://github.com/azjezz/web-php-mock-ups
On 07.02.2019 at 16:14, Sjon Hortensius wrote:
> On Wed, Feb 6, 2019 at 4:14 PM Ben Ramsey wrote:
>
>>> On Feb 6, 2019, at 01:22, Peter Kokot wrote:
>>> I can help sort this mess. A separate fork out of the php/php-src was
>>> not such a good idea.
>>
>> Sorry. I made many poor decisions around
On Wed, Feb 6, 2019 at 4:14 PM Ben Ramsey wrote:
> > On Feb 6, 2019, at 01:22, Peter Kokot wrote:
> > I can help sort this mess. A separate fork out of the php/php-src was
> > not such a good idea.
>
> Sorry. I made many poor decisions around how I managed that entire event.
> It’s my own person
Am 07.02.2019 um 14:28 schrieb Rowan Collins :
> On 7 February 2019 11:19:46 GMT+00:00, Benjamin Morel
> wrote:
>> Also, some applications might assume that the directory does not already
>> exist, and want to fail if it does. So both use cases must be available in
>> the API.
mkdir("foo") or f
On 7 February 2019 08:38:54 GMT+00:00, Zeev Suraski wrote:
>> It's the only definition we currently have.
>
>That's not exactly true. We have the definition that was actually
>agreed
>upon in the original Voting RFC, and while it's hardly great - it's
>clearly
>different from the voting base we c
On 7 February 2019 11:19:46 GMT+00:00, Benjamin Morel
wrote:
>Also, some applications might assume that the directory does not
>already
>exist, and want to fail if it does. So both use cases must be available
>in
>the API.
I absolutely agree, but I also agree that the task here is not "convert
Hi,
The PHP development team announces the immediate availability of PHP
7.2.15. This is a bugfix release.
All PHP 7.2 users are encouraged to upgrade to this version.
For source downloads of PHP 7.2.15 please visit our downloads page.
Windows binaries can be found on the PHP for Windows site.
T
Hello,
On 2018-12-13 17:52, Rainer Jung wrote:
> I might be wrong, but I vaguely remember that PHp does not call
> "pkg-config --static --libs openssl" with a correctly setup
> PKG_CONFIG_PAATZ to get the libs needed for static compilation.
> Typically OpenSSL installs correct pc files that contai
On Thu, Feb 7, 2019 at 10:42 AM Pierre Joye wrote:
> On Thu, Feb 7, 2019 at 3:39 PM Zeev Suraski wrote:
>
> > It has to do with the relative power
> > of the code contributors, vs. folks who aren't code contributors who
> > presently have a vote even though they're not supposed to have one base
On Thu, 7 Feb 2019 at 11:08, Benjamin Morel
wrote:
> Plus, as I stated earlier, I'm confident that typed properties will give
> much more credit to this approach, as we'll get an immediate Error should
> we accidentally access an uninitialized property, as opposed to a null
> value previously.
>
The PHP development team announces the immediate availability of PHP
7.3.2. This is a bugfix release with several bug fixes included.
All PHP 7.3 users are encouraged to upgrade to this version.
For source downloads of PHP 7.3.2 please visit our downloads page.
Windows binaries can be found on th
>
> Please don't do that either, I don't want to convert
> @mkdir("foo");
> to
> try { mkdir("foo"); } catch (Exception $e) {}
> just to stop my script from exiting if the directory already exists.
What you really want is either another function that does not throw an
exception in
Hey Ben,
FWIW, I also worked on a similar feature via transparent proxying (never
finished though): it is an edge case that can be handled in userland, and
it doesn't need to be performance sensitive ("edge case"), since the
trade-off is more CPU vs less I/O and memory usage (skip loading of LOB
f
>
> So this entire feature request is to support something which the Doctrine
> manual spends several paragraphs saying you should probably never use?
If Doctrine authors thought that you should *never *use it, they would
never have added the feature in the first place. They just place a big
cave
On Thu, 7 Feb 2019 at 09:35, Benjamin Morel
wrote:
> apologies if I've missed it, but have you actually said what that use case
>> is?
>
>
> Sorry if it wasn't clear in my original post. The use case is the
> following:
>
> - a data mapper retrieves an object from the database
> - for optimizatio
All,
I've read the detailed and very informative feedback from both Pierre and
Dan, as well as feedback from others (Nikita & more) over the last few
days, and I'm now convinced that breaking the Voting part away from the
Workflow part is the right way forward. Not because ideally they shouldn't
>
> apologies if I've missed it, but have you actually said what that use case
> is?
Sorry if it wasn't clear in my original post. The use case is the following:
- a data mapper retrieves an object from the database
- for optimization purposes, we can ask the data mapper to return a partial
obje
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 use and it prov
Am 07.02.2019 um 10:01 schrieb Benjamin Morel :
> IMO, @ can be safely removed the day PHP converts current warnings to
> exceptions.
Please don't do that either, I don't want to convert
@mkdir("foo");
to
try { mkdir("foo"); } catch (Exception $e) {}
just to stop my script from ex
>
> That is one the cases I meant. Also this is a bug in the user code. I can
> imagine doing it on purpose for performance reasons (if the file is
> created/deleted by other apps) tho'.
> flock is what should be used here.
flock doesn't protect from other failures, such as a fread()ing a file
l
On Thu, Feb 7, 2019 at 3:39 PM Zeev Suraski wrote:
> It has to do with the relative power
> of the code contributors, vs. folks who aren't code contributors who
> presently have a vote even though they're not supposed to have one based on
> the rules agreed upon back in the day.
This is not cor
On Wed, Feb 6, 2019 at 9:06 PM Niklas Keller wrote:
> > I'll reiterate my main two issues with this RFC:
> > - I do think that we need 50%+1 votes for certain decisions. Naming the
> > next version of PHP, or even deciding to release it outside of the yearly
> > cycle should not require a 2/3 vo
On Thu, Feb 7, 2019 at 3:14 PM Christian Schneider
wrote:
>
> Am 07.02.2019 um 02:32 schrieb Pierre Joye :
> > On Thu, Feb 7, 2019, 8:07 AM Girgias >> The most common case which comes to mind is to suppress erros while file
> >> reading.
> >> Because even if you check a file exists it could be d
Am 07.02.2019 um 02:32 schrieb Pierre Joye :
> On Thu, Feb 7, 2019, 8:07 AM Girgias > The most common case which comes to mind is to suppress erros while file
>> reading.
>> Because even if you check a file exists it could be deleted inbetween the
>> check and the
>> read command. As you can see
31 matches
Mail list logo
