> Am 05.02.2019 um 16:16 schrieb Sven Van Caekenberghe <s...@stfx.eu>:
>
> Still, there are advantages to an in-image solution, can't says this enough,
> these external lib dependencies pose their own problems ...
+1
>
>> On 5 Feb 2019, at 08:33, Esteban Lorenzano <esteba...@gmail.com> wrote:
>>
>> Hi,
>>
>> Yes, Pharo regex implementation is very naive.
>> We will be moving to a PCRE binding to match outside world standards but we
>> have not had the time to work on it :(
>>
>> Esteban
>>
>>> On 5 Feb 2019, at 00:27, Manuel Leuenberger <leuenber...@inf.unibe.ch>
>>> wrote:
>>>
>>> Hi,
>>>
>>> I just noticed that the Pharo regexes do not understand non-greedy matches.
>>> A regex engine to be PCRE is kind of essential, not having '.*?' to be a
>>> parseable and working regex is a bummer. Are there any more powerful regex
>>> engines around for Pharo? I could not find any.
>>>
>>> Cheers,
>>> Manuel
>>>
>>>
>>
>>
>
>
