Re: Parsing unnamed parameters from urls

2016-10-18 Thread Keisuke Miyako
> Matches letters, digits and underscores. Equivalent to [A-Za-z0-9_]. I suppose that is a good enough definition. according to the docs: > Match a word character. Word characters are > [\p{Alphabetic}\p{Mark}\p{Decimal_Number}\p{Connector_Punctuation}\u200c\u200d]. http://userguide.icu-projec

Re: Parsing unnamed parameters from urls

2016-10-18 Thread Lee Hinde
I'll try it, but the cheat sheet I was using said that w Matches letters, digits and underscores. Equivalent to [A-Za-z0-9_]. On Mon, Oct 17, 2016 at 8:45 PM, Keisuke Miyako wrote: > would it not be safer to specify > > [^/]* = "anything but a forward slash" > > instead of \\w which can match w

Re: Parsing unnamed parameters from urls

2016-10-17 Thread Keisuke Miyako
would it not be safer to specify [^/]* = "anything but a forward slash" instead of \\w which can match word breaks other than a forward slash? > 2016/10/18 10:00、Lee Hinde のメール: > > $match:="/api/(\\w+)/(\\w+)/" 宮古 啓介 セールス・エンジニア 株式会社フォーディー・ジャパン 〒150-0043 東京都渋谷区道玄坂1-10-2 渋谷THビル6F Tel: 03-642

Re: Parsing unnamed parameters from urls

2016-10-17 Thread David Adams
For a different take, here's the old school version I get to parse URL items into an array: // WebRequest_ParseURLItems // Strip parameters off URL and parse the remainder into items. // 4D automatically URL decodes the incoming data before it arrives. // Otherwise, this routine would need to conv