Hi Dan,
Sorry for keep posting broken English.
I shouldn't difficult.
>
It shouldn't be difficult.
Looking forward more than handful, useful and common hash_hkdf()
application
examples for PHP that justify the API. If you would not like to spend time
for working
code, just ideas are OK also.
R
Hi Dan,
I appreciate your feedback, regardless of your opinion towards this issue.
On Wed, Sep 6, 2017 at 8:04 PM, Dan Ackroyd wrote:
> On 6 September 2017 at 02:15, Yasuo Ohgaki wrote:
> > What should we do for this?
>
> Not us, you.
>
OK. It is recorded that you think current API is totally
> On Sep 6, 2017, at 18:45, Andrea Faulds wrote:
> Would anyone object to me changing how PHP handles this so that only the
> final ?> tag consumes its following newline, and only at the end of the file?
>
I object. It's a change in ancient behavior that has the potential to break
existing c
Hi Dan
On Wed, Sep 6, 2017 at 8:38 PM, Dan Ackroyd wrote:
> On 6 September 2017 at 12:15, Rowan Collins
> wrote:
>
> > If you have suggestions for how the format should look
>
> Don't use a format. Just write code - see below.
>
> > Which is why Yasuo and I have both suggested we work together
Hi everyone,
This is the tiniest of issues, but it's bugged me for a long time and
makes the HTML produced by PHP code less readable than it out to be.
Specifically, PHP ignores a newline immediately following a ?> tag. The
reason for this is, from what I recall, to prevent issues where
white
Results for project PHP master, build date 2017-09-05 19:23:47-07:00
commit: dfe0300
previous commit:002856c
revision date: 2017-09-05 18:14:21+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
On 6 September 2017 21:33:53 BST, Dan Ackroyd wrote:
>On 6 September 2017 at 13:31, Rowan Collins
>wrote:
>> I'm going to assume that the code you posted was something of a straw
>> man, and you're not actually advocating people copy 20 lines of code
>for
>> every variable they want to validate.
On 6 September 2017 at 13:31, Rowan Collins wrote:
> I'm going to assume that the code you posted was something of a straw
> man, and you're not actually advocating people copy 20 lines of code for
> every variable they want to validate.
You assume wrong. No it's not, and yes I am.
I can point a
Hi!
> That would be fine and appropriate. The RFC targets 7.3. Having a
> discussion and vote in March gives plenty of time for getting it into
> 7.3
>
> Cancelling a vote just to avoid an RFC being rejected is (imo) playing
> slightly fast and loose with the rules.
I agree. I think the RFC itse
On Wed, Sep 6, 2017 at 11:30 AM, François Laupretre
wrote:
>> Secondly, ideally, this shouldn't just be a mechanism to mix and match C
>> and PHP - but actually make it easy for people to write pure PHP code
>> that'll become integrated to the PHP binary. PCS can practically already
>> support th
Hi Zeev,
Le 06/09/2017 à 16:01, Zeev Suraski a écrit :
Thanks for the pointer! I didn't pay close attention to that discussion
back then. I do remember François brought it up in a discussion back in
2015 in Paris.
For me the issue of security is a major benefit that I don't think was
brought u
On 06/09/17 13:46, Zeev Suraski wrote:
> We’d probably have to be pretty selective in terms of what goes in there –
> probably just as selective as we are with the C-based extensions, but I’d
> imagine that things like ext/exif, UUID, and perhaps even things like
> unserialize() could find thems
On Wed, Sep 6, 2017 at 4:19 PM, Nikita Popov wrote:
> On Wed, Sep 6, 2017 at 2:46 PM, Zeev Suraski wrote:
>
> > I think that actually makes a lot of sense, and not just because of the
> > supportability – but also because of security. A whole class of security
> > exploits – buffer/stack overfl
On Wed, Sep 6, 2017 at 2:46 PM, Zeev Suraski wrote:
> I think that actually makes a lot of sense, and not just because of the
> supportability – but also because of security. A whole class of security
> exploits – buffer/stack overflows, underruns and all sorts of memory
> mismanagement become i
Le 06/09/2017 à 14:46, Zeev Suraski a écrit :
> We could create a mechanism where the contents of certain .php files is
> embedded into the binary, compiled during MINIT, and made available pretty at
> the same ‘builtinness’ level as C extensions.
Just for memory, an implementation already exi
I think that actually makes a lot of sense, and not just because of the
supportability – but also because of security. A whole class of security
exploits – buffer/stack overflows, underruns and all sorts of memory
mismanagement become irrelevant when the code is implemented in PHP. I brought
On 6 September 2017 12:52:24 BST, Lester Caine wrote:
>On 06/09/17 12:15, Rowan Collins wrote:
>> On 6 September 2017 09:29:37 BST, Lester Caine
>wrote:
>> Which is why Yasuo and I have both suggested we work together to come
>up with such a standard format that can be used or adapted for these
>
On 6 September 2017 12:38:03 BST, Dan Ackroyd wrote:
>On 6 September 2017 at 12:15, Rowan Collins
>wrote:
>
>> If you have suggestions for how the format should look
>
>Don't use a format. Just write code - see below.
I'm going to assume that the code you posted was something of a straw man, and
On 06/09/17 13:00, li...@rhsoft.net wrote:
> Am 06.09.2017 um 13:52 schrieb Lester Caine:
>> The likes of ADOdb datadict are still used as a base for metadata in
>> projects, but PDO destroyed the standardisation that used to exist by
>> spawning a number of competing wrappers. https://github.com/A
> On 6 Sep 2017, at 18:15, Rowan Collins wrote:
>
>> On 6 September 2017 09:29:37 BST, Lester Caine wrote:
>> My only problem with Yasuo's latest offering is once again it adds a
>> whole new set of defines that have to be mapped to existing metadata
>> definitions ... That and it is a lot of l
Am 06.09.2017 um 13:52 schrieb Lester Caine:
The likes of ADOdb datadict are still used as a base for metadata in
projects, but PDO destroyed the standardisation that used to exist by
spawning a number of competing wrappers. https://github.com/ADOdb/ADOdb
has evolved from a private project to b
On 06/09/17 12:15, Rowan Collins wrote:
> On 6 September 2017 09:29:37 BST, Lester Caine wrote:
>> My only problem with Yasuo's latest offering is once again it adds a
>> whole new set of defines that have to be mapped to existing metadata
>> definitions ... That and it is a lot of longhand code u
I'd seriously start considering to start doing PHP code for things like
these, so they are not bogged down by the fact that they are in C and there
is 0.5 devs interested in supporting it.
On Wed, 6 Sep 2017, 14:09 Dan Ackroyd wrote:
> On 5 September 2017 at 18:24, Fleshgrinder wrote:
> > Maybe
On 6 September 2017 at 12:15, Rowan Collins wrote:
> If you have suggestions for how the format should look
Don't use a format. Just write code - see below.
> Which is why Yasuo and I have both suggested we work together
If you're going to work together and continue the conversation, please
ca
On 6 September 2017 09:29:37 BST, Lester Caine wrote:
>My only problem with Yasuo's latest offering is once again it adds a
>whole new set of defines that have to be mapped to existing metadata
>definitions ... That and it is a lot of longhand code using a different
>style to existing arrays. We n
On 5 September 2017 at 18:24, Fleshgrinder wrote:
> Maybe I should stop the vote. The discussion is happening now instead of
> before when I asked for it. We'll have to wait for at least six months
> for another vote if this is a no, due to the rules.
That would be fine and appropriate. The RFC t
On 6 September 2017 at 02:15, Yasuo Ohgaki wrote:
> What should we do for this?
Not us, you.
You should start listening to other people's feedback.
You continually refuse to accept any feedback that doesn't agree with
your world-view, not only on the subject of hkdf, but on validation
and other
Granted, sorry about delay.
Cheers
Joe
On Sat, Jul 22, 2017 at 5:46 PM, Andreas Treichel wrote:
> Hi,
>
> I registered my wiki account "Blar" and need some karma for my first RFC
> for new cookie functions. I already posted some infos about
> "http_cookie_set and http_cookie_remove" on the mail
Granted, sorry about delay.
Cheers
Joe
On Fri, Sep 1, 2017 at 3:10 AM, BohwaZ/PHP wrote:
> 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/pu
On 05/09/17 21:45, Rowan Collins wrote:
>> I've been pushing the idea of a single method of managing metadata for
>> a long time.
>> A single standard set of rules
>> that can be used across the board from variable creation to checking
>> data going out to forms and returns coming back and data be
On Di., 5. Sep. 2017, 21:32 Andreas Heigl wrote:
> Hey Richard
>
> Am 05.09.17 um 19:29 schrieb Fleshgrinder:
> > On 9/5/2017 7:01 PM, Andreas Heigl wrote:
> >> Hey Richard, Hey all.
> >>
> >> Thanks for putting up the RFC and the implementation!
> >>
> >> Having UUIDs in the core would be awesom
31 matches
Mail list logo
