On 12/06/2013 8:52 a.m., Kinkie wrote:
On Tue, Jun 11, 2013 at 5:00 PM, Alex Rousskov
wrote:
On 06/11/2013 02:23 AM, Kinkie wrote:
On Mon, Jun 10, 2013 at 7:22 PM, Alex Rousskov
wrote:
On 06/09/2013 02:40 PM, Kinkie wrote:
while attempting to increase portability to recent clang release
On Tue, Jun 11, 2013 at 5:00 PM, Alex Rousskov
wrote:
> On 06/11/2013 02:23 AM, Kinkie wrote:
>> On Mon, Jun 10, 2013 at 7:22 PM, Alex Rousskov
>> wrote:
>>> On 06/09/2013 02:40 PM, Kinkie wrote:
>>>
while attempting to increase portability to recent clang releases, I
noticed that lib
On 06/11/2013 02:23 AM, Kinkie wrote:
> On Mon, Jun 10, 2013 at 7:22 PM, Alex Rousskov
> wrote:
>> On 06/09/2013 02:40 PM, Kinkie wrote:
>>
>>> while attempting to increase portability to recent clang releases, I
>>> noticed that libTrie hasn't benefited from the portability work that
>>> was do
On 11/06/2013 8:54 p.m., Robert Collins wrote:
On 11 June 2013 20:23, Kinkie wrote:
On Mon, Jun 10, 2013 at 7:22 PM, Alex Rousskov wrote:
From what I understand (Robert, can you come to the rescue?) libTrie
is a very optimized key- and prefix- lookup engine, trading memory
useage for speed. It
On 11 June 2013 20:23, Kinkie wrote:
> On Mon, Jun 10, 2013 at 7:22 PM, Alex Rousskov
> wrote:
> From what I understand (Robert, can you come to the rescue?) libTrie
> is a very optimized key- and prefix- lookup engine, trading memory
> useage for speed. It would be great to use in the Http pars
On 6/11/2013 11:23 AM, Kinkie wrote:
On Mon, Jun 10, 2013 at 7:22 PM, Alex Rousskov
wrote:
On 06/09/2013 02:40 PM, Kinkie wrote:
while attempting to increase portability to recent clang releases, I
noticed that libTrie hasn't benefited from the portability work that
was done in the past fe
On Mon, Jun 10, 2013 at 7:22 PM, Alex Rousskov
wrote:
> On 06/09/2013 02:40 PM, Kinkie wrote:
>
>> while attempting to increase portability to recent clang releases, I
>> noticed that libTrie hasn't benefited from the portability work that
>> was done in the past few years.
>>
>> I can see three
On 06/09/2013 02:40 PM, Kinkie wrote:
> while attempting to increase portability to recent clang releases, I
> noticed that libTrie hasn't benefited from the portability work that
> was done in the past few years.
>
> I can see three ways to move forward:
> 1- replicate these changes into libTr
