Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:127135
Precedence: bulk
MIME-Version: 1.0
References: <CAH5C8xUb1O20ZDrOQNC=ckFxHUUWSK7sw_njQQzFBd0qgQqoww@mail.gmail.com>
 <dd61999c-1ebd-4765-9add-cd8065968965@gmail.com> <CAOV5rgYZ_s1of-igLFEK7oqqh6=3HeYv0=JvvKvvjkcp0F6Q9Q@mail.gmail.com>
 <CAH5C8xV67frqOBCvLt73RM7QO86_pu40sHP5h71_kDRbKPtA8Q@mail.gmail.com>
 <1BCB4144-231D-45EA-A914-98EE8F0F503A@automattic.com> <8E614C9C-BA85-45D8-9A4E-A30D69981C5D@automattic.com>
 <CAH5C8xV69pHnSKWJrVB8EQab7vPhcaXAwYezoG6z3Oj7ZkXBaQ@mail.gmail.com>
 <bc5472e39bc607e2c7accc9d2bd6f239@bastelstu.be> <CAH5C8xW_auVf+ig7odhTK8dVWwmXTg4ZVZN-0Fhh4SUBzrWxVw@mail.gmail.com>
 <8df04e01-deac-404b-beb7-cd982423db63@bastelstu.be> <CAH5C8xU0JcnmC2Hdd=Hj0CQUaL0-LN=1X8+5-eUbFH3ZMxCvBA@mail.gmail.com>
 <33427cd03035ef084245c44290b56a55@bastelstu.be> <CAH5C8xXwDO6Ui8pLmqoxEguURh97fAaL4CfLK-oitqC85N7+8w@mail.gmail.com>
 <0aa1eefc3941bdea0092e935074daa58@bastelstu.be> <CAH5C8xU+rnp4e5=CzqhEncRww6nhZ7x1s68NjWtu+HQMpoNZ8g@mail.gmail.com>
 <CAOV5rgbV4apngGT6Ue4QyTthZ-dA2w59VYHmiwYjgNeSRiK5Gg@mail.gmail.com>
In-Reply-To: <CAOV5rgbV4apngGT6Ue4QyTthZ-dA2w59VYHmiwYjgNeSRiK5Gg@mail.gmail.com>
Date: Thu, 17 Apr 2025 13:53:34 +0200
Message-ID: <CAH5C8xUOoOHKLcLO0qCVYaVDJw1gPmrdy2x1oohHQcRs+B8TPA@mail.gmail.com>
Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API
To: ignace nyamagana butera <nyamsprod@gmail.com>
Cc: =?UTF-8?Q?Tim_D=C3=BCsterhus?= <tim@bastelstu.be>, 
	Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e28f300632f80d28"
From: kocsismate90@gmail.com (=?UTF-8?B?TcOhdMOpIEtvY3Npcw==?=)

--000000000000e28f300632f80d28
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Ignace,


> Currently the path is nullable but according to the RFC the path can not
> be nullable
> According to the RFC the path can have up to 5 ABNF representation
>

Uh, this is something that I also forgot to sync between the implementation
and the RFC. I also recently found out that
the get*Path() methods should be non-nullable for both classes, so I
recently fixed them. Sorry for the confusion!

Regards,
M=C3=A1t=C3=A9

--000000000000e28f300632f80d28
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Hi Ignace,</div><div class=3D"gmail_quote=
 gmail_quote_container"><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div>Currently the path is nullable but ac=
cording to the RFC the path can not be nullable=C2=A0</div><div>According t=
o the RFC the path can have up to 5 ABNF representation</div></div></blockq=
uote><div><br></div><div>Uh, this is something that I also forgot to sync b=
etween the implementation and the RFC. I also recently found out that</div>=
<div>the get*Path() methods should be non-nullable for both classes, so I r=
ecently fixed them. Sorry for the confusion!</div><div><br></div><div>Regar=
ds,</div><div>M=C3=A1t=C3=A9</div><div>=C2=A0</div></div></div>

--000000000000e28f300632f80d28--