Re: [PHP-DEV] Re: Checkout phpdoc

[Andreas Heigl]

Am 25. Juni 2019 23:41:42 MESZ schrieb Benjamin Morel 
:
>By the way, is there any work in progress to migrate the PHP manual to
>Git?
>The docs only say:
>
>The PHP manual is still currently hosted on SVN, although it will be
>> migrated to Git in the future.
>
>
>I'd love to be able to fix things in the PHP manual with a simple PR;
>the
>current process has always repelled me.
>
>Ben
>
>On Tue, 25 Jun 2019 at 11:10, Sascha Schumann <
>sascha.schum...@myrasecurity.com> wrote:
>
>> I have disabled SNI for the upstreams on svn2.php.net.
>>
>> If the problem persists, please provide a way to reproduce the issue.
>>
>> Thanks
>> Sascha

There is a small team of people currently working on moving the docs to git.

Due to the tight integration of SVN into the workflow it's not as easy as we 
all thought to do the actual move.

For more infos feel free to head over to https://github.com/phpdoctest/meta

Cheers

Andreas

-- 
  ,,,
 (o o)
+-ooO-(_)-Ooo-+
| Andreas Heigl   |
| mailto:andr...@heigl.org  N 50°22'59.5" E 08°23'58" |
| https://andreas.heigl.org https://bit.ly/wiFKy7 |
+-+

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Re: Checkout phpdoc

[Benjamin Morel]

Can't wait to try it, thanks for the pointer!

Ben

On Tue, 25 Jun 2019 at 23:48, G. P. B.  wrote:

> On Tue, 25 Jun 2019 at 23:41, Benjamin Morel 
> wrote:
>
>> By the way, is there any work in progress to migrate the PHP manual to
>> Git?
>> The docs only say:
>>
>> The PHP manual is still currently hosted on SVN, although it will be
>> > migrated to Git in the future.
>>
>>
>> I'd love to be able to fix things in the PHP manual with a simple PR; the
>> current process has always repelled me.
>>
>> Ben
>
>
> I think there is a way to do a GitHub PR atm via
> https://github.com/php/doc-en/pulls
>
> George P. Banyard
>

Re: [PHP-DEV] Re: Checkout phpdoc

[G. P. B.]

 On Tue, 25 Jun 2019 at 23:41, Benjamin Morel 
wrote:

> By the way, is there any work in progress to migrate the PHP manual to Git?
> The docs only say:
>
> The PHP manual is still currently hosted on SVN, although it will be
> > migrated to Git in the future.
>
>
> I'd love to be able to fix things in the PHP manual with a simple PR; the
> current process has always repelled me.
>
> Ben


I think there is a way to do a GitHub PR atm via
https://github.com/php/doc-en/pulls

George P. Banyard

Re: [PHP-DEV] Re: Checkout phpdoc

[Benjamin Morel]

By the way, is there any work in progress to migrate the PHP manual to Git?
The docs only say:

The PHP manual is still currently hosted on SVN, although it will be
> migrated to Git in the future.


I'd love to be able to fix things in the PHP manual with a simple PR; the
current process has always repelled me.

Ben

On Tue, 25 Jun 2019 at 11:10, Sascha Schumann <
sascha.schum...@myrasecurity.com> wrote:

> I have disabled SNI for the upstreams on svn2.php.net.
>
> If the problem persists, please provide a way to reproduce the issue.
>
> Thanks
> Sascha

Re: [PHP-DEV] [RFC] Strict operators directive

[Joe Watkins]

Evening,

There doesn't seem to be a patch or implementation.

Aside from the proposed semantics, which I can't really read because the
document is malformed, the most important questions for me are: How is this
going to work? Can it be done without significant complexity in the
compiler or VM?

Without an implementation I can't really consider the ideas proposed,
because they are just ideas without proof that they are reasonably
implementable.

While you can technically move forward with an RFC without implementation,
in this case the implementation should inform our decision at vote time.

Cheers
Joe


On Tue, 25 Jun 2019, 23:19 Benjamin Morel,  wrote:

> Impressive work indeed, this would be a perfect addition to strict_types
> that would remove a lot of WTFs while preserving BC with older code.
>
> Please note that the formatting of the RFC is broken after the Bitwise
> Operators section.
>
> Ben
>

Re: [PHP-DEV] [RFC] Strict operators directive

[Benjamin Morel]

Impressive work indeed, this would be a perfect addition to strict_types
that would remove a lot of WTFs while preserving BC with older code.

Please note that the formatting of the RFC is broken after the Bitwise
Operators section.

Ben

Re: [PHP-DEV] [RFC] Strict operators directive

[Arnold Daniels]

On Tue, Jun 25, 2019 at 7:56 PM Guilliam Xavier 
wrote:

> On Tue, Jun 25, 2019 at 3:09 PM Arnold Daniels
>  wrote:
> >
> > Hi all,
> >
> > I would like to open the discussion for RFC: "Strict operators
> directive".
> >
> > This RFC proposes a new directive 'strict_operators'. When enabled,
> operators may cast operands to the expected type, but must comply to;
> >
> > * Typecasting is not based on the type of the other operand
> >
> > * Typecasting is not based on the value of any of the operands
> > * Operators will throw a TypeError for unsupported types
> >
> > Reasoning; The current rules for type casting done by operators are
> inconsistent and complex, which can lead to surprising results where a
> statement seemingly contradicts itself.
> >
> > Using a directive means that backwards compatibility is guaranteed.
> >
> > https://wiki.php.net/rfc/strict_operators
> >
> > Yours,
> > Arnold Daniels
> >
> > [Arnold Daniels - Chat @ Spike](
> https://www.spikenow.com/?ref=spike-organic-signature&_ts=1mzl6)
> [1mzl6]
>
> Hello, thanks for the impressive work...
> I have just one interrogation: why disallow `~` for strings?
> (e.g. currently `~"\x00\x01\x02"` gives `"\xFF\xFE\xFD"`)
>
> --
> Guilliam Xavier
>

Using `~` for strings should be allowed.  I fixed it in the RFC.

Well spotted.

- Arnold

Re: [PHP-DEV] [RFC] Strict operators directive

[Guilliam Xavier]

On Tue, Jun 25, 2019 at 3:09 PM Arnold Daniels
 wrote:
>
> Hi all,
>
> I would like to open the discussion for RFC: "Strict operators directive".
>
> This RFC proposes a new directive 'strict_operators'. When enabled, operators 
> may cast operands to the expected type, but must comply to;
>
> * Typecasting is not based on the type of the other operand
>
> * Typecasting is not based on the value of any of the operands
> * Operators will throw a TypeError for unsupported types
>
> Reasoning; The current rules for type casting done by operators are 
> inconsistent and complex, which can lead to surprising results where a 
> statement seemingly contradicts itself.
>
> Using a directive means that backwards compatibility is guaranteed.
>
> https://wiki.php.net/rfc/strict_operators
>
> Yours,
> Arnold Daniels
>
> [Arnold Daniels - Chat @ 
> Spike](https://www.spikenow.com/?ref=spike-organic-signature&_ts=1mzl6)   
>  [1mzl6]

Hello, thanks for the impressive work...
I have just one interrogation: why disallow `~` for strings?
(e.g. currently `~"\x00\x01\x02"` gives `"\xFF\xFE\xFD"`)

-- 
Guilliam Xavier

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] [RFC] Strict operators directive

[Arnold Daniels]

Hi all,

I would like to open the discussion for RFC: "Strict operators directive".

This RFC proposes a new directive 'strict_operators'. When enabled, operators 
may cast operands to the expected type, but must comply to;

* Typecasting is not based on the type of the other operand

* Typecasting is not based on the value of any of the operands
* Operators will throw a TypeError for unsupported types

Reasoning; The current rules for type casting done by operators are 
inconsistent and complex, which can lead to surprising results where a 
statement seemingly contradicts itself.

Using a directive means that backwards compatibility is guaranteed.

https://wiki.php.net/rfc/strict_operators

Yours,
Arnold Daniels

[Arnold Daniels - Chat @ 
Spike](https://www.spikenow.com/?ref=spike-organic-signature&_ts=1mzl6)
[1mzl6]

Re: [PHP-DEV] Re: Checkout phpdoc

[Sascha Schumann]

I have disabled SNI for the upstreams on svn2.php.net.

If the problem persists, please provide a way to reproduce the issue.

Thanks
Sascha

Re: [PHP-DEV] Re: Checkout phpdoc

[Peter Cowburn]

+Sascha

On Tue, 25 Jun 2019 at 08:46, Christoph M. Becker  wrote:

> On 25.06.2019 at 04:43, Arnold Daniels wrote:
>
> > I'm trying to checkout phpdoc using SVN, but I'm getting the error
> "Unexpected HTTP status 421 'Misdirected Request'".
> >
> > Is something broken? Or am I doing it wrong?
>

It looks like something is wrong due to the recently added CDN in front of
the SVN server.  If I make a request, I get the following response:

HTTP/1.1 421 Misdirected Request
Server: myracloud
Date: Tue, 25 Jun 2019 07:57:41 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 400
Connection: keep-alive
Expires: Tue, 25 Jun 2019 07:57:41 GMT
Cache-Control: max-age=0



421 Misdirected Request

Misdirected Request
The client needs a new connection for this
request as the requested host name does not match
the Server Name Indication (SNI) in use for this
connection.

Apache/2.4.25 (Debian) Server at svn.php.net Port 443


Sascha, any ideas?


> >
> > - Arnold
> >
> > $ svn co http://svn.php.net/repository/phpdoc/modules/doc-en phpdoc
> > A phpdoc/build.sh
> > U phpdoc
> >
> > Fetching external item into 'phpdoc/doc-base':
> > A phpdoc/doc-base/entities
> > A phpdoc/doc-base/entities/ISO
> > A phpdoc/doc-base/scripts
> > A phpdoc/doc-base/scripts/docgen
> > svn: warning: W175002: Unexpected HTTP status 421 'Misdirected Request'
> on
> '/repository/!svn/rvr/336013/phpdoc/doc-base/trunk/scripts/docgen/constructor.tpl'
> >
> > Fetching external item into 'phpdoc/en':
> > svn: warning: W175002: Unexpected HTTP status 421 'Misdirected Request'
> on '/repository/phpdoc/en/trunk'
> >
> > Checked out revision 347656.
> > svn: E205011: Failure occurred processing one or more externals
> definitions
> >
> > [Arnold Daniels - Chat @ Spike](
> https://www.spikenow.com/?ref=spike-organic-signature&_ts=1m6kq)
> [1m6kq]
>
> Nikita reported similar issues not long ago, but AFAIR these have been
> resolved; only sometimes intermittent checkout errors still occur.
> Please try to checkout again.
>
> Thanks,
> Christoph
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

[PHP-DEV] Re: Checkout phpdoc

[Christoph M. Becker]

On 25.06.2019 at 04:43, Arnold Daniels wrote:

> I'm trying to checkout phpdoc using SVN, but I'm getting the error 
> "Unexpected HTTP status 421 'Misdirected Request'".
>
> Is something broken? Or am I doing it wrong?
>
> - Arnold
>
> $ svn co http://svn.php.net/repository/phpdoc/modules/doc-en phpdoc
> A phpdoc/build.sh
> U phpdoc
>
> Fetching external item into 'phpdoc/doc-base':
> A phpdoc/doc-base/entities
> A phpdoc/doc-base/entities/ISO
> A phpdoc/doc-base/scripts
> A phpdoc/doc-base/scripts/docgen
> svn: warning: W175002: Unexpected HTTP status 421 'Misdirected Request' on 
> '/repository/!svn/rvr/336013/phpdoc/doc-base/trunk/scripts/docgen/constructor.tpl'
>
> Fetching external item into 'phpdoc/en':
> svn: warning: W175002: Unexpected HTTP status 421 'Misdirected Request' on 
> '/repository/phpdoc/en/trunk'
>
> Checked out revision 347656.
> svn: E205011: Failure occurred processing one or more externals definitions
>
> [Arnold Daniels - Chat @ 
> Spike](https://www.spikenow.com/?ref=spike-organic-signature&_ts=1m6kq)  
> [1m6kq]

Nikita reported similar issues not long ago, but AFAIR these have been
resolved; only sometimes intermittent checkout errors still occur.
Please try to checkout again.

Thanks,
Christoph


--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php