On 07/29/2013 06:31 PM, Amos Jeffries wrote:
> On 30/07/2013 5:25 a.m., Amos Jeffries wrote:
>> Attached is a patch which adds a secondary form of undo for handling
>> incorrectly identified ConfigParser::FunctionNameToken elements.
>> Instead of aborting Squid on any non-function token containing
On 30/07/2013 5:25 a.m., Amos Jeffries wrote:
Looks like nobody actually ran the trivial "-k parse" test using
3.HEAD or the initial quoted strings code.
Attached is a patch which adds a secondary form of undo for handling
incorrectly identified ConfigParser::FunctionNameToken elements.
Inste
On 07/29/2013 02:13 PM, Amos Jeffries wrote:
> On 30/07/2013 6:40 a.m., Alex Rousskov wrote:
>> After this patch, if I type parametres(foo) instead of parameters(foo),
>> will Squid think that I am defining a regular expression instead of
>> importing foo where my true regular expressions are store
On 07/29/2013 01:42 PM, Kinkie wrote:
>> After this patch, if I type parametres(foo) instead of parameters(foo),
>> will Squid think that I am defining a regular expression instead of
>> importing foo where my true regular expressions are stored?
> Guys, one question: I understand that everyone h
On 07/29/2013 01:38 PM, Kinkie wrote:
> So to implement this I should:
> - rename current reserveSpace to rawSpace, add returning the pointer
> as in current rawSpace.
> - reimplement reserveSpace as a convenience calling reserveCapacity
> - adjust clients of reserveSpace to use rawSpace instead.
On 29/07/2013 11:05 p.m., Eliezer Croitoru wrote:
I am building the new beta and it seems to configure and build nicely on
CentOS 6.4 x64 but only when building manually.
When I built it using the squid.spec that was being used with 3.3.8 I
started getting some SNMP problem.
output:
---
libto
On 30/07/2013 7:42 a.m., Kinkie wrote:
After this patch, if I type parametres(foo) instead of parameters(foo),
will Squid think that I am defining a regular expression instead of
importing foo where my true regular expressions are stored?
Guys, one question: I understand that everyone here is ve
On 30/07/2013 6:40 a.m., Alex Rousskov wrote:
On 07/29/2013 11:25 AM, Amos Jeffries wrote:
Looks like nobody actually ran the trivial "-k parse" test using 3.HEAD
or the initial quoted strings code.
Or perhaps nobody ran such a test with non-trivial regular expressions
in squid.conf? I know I t
> After this patch, if I type parametres(foo) instead of parameters(foo),
> will Squid think that I am defining a regular expression instead of
> importing foo where my true regular expressions are stored?
Guys, one question: I understand that everyone here is very
distrusting of lex/yacc parser g
On Mon, Jul 29, 2013 at 5:32 PM, Alex Rousskov
wrote:
> On 07/29/2013 03:02 AM, Kinkie wrote:
>> On Sat, Jul 27, 2013 at 8:31 PM, Alex Rousskov wrote:
>> 1a. Reserve total buffer capacity. Ensure exclusive buffer ownership.
>>
>> 1b. Reserve buffer space. Ensure exclusi
On 07/29/2013 11:25 AM, Amos Jeffries wrote:
> Looks like nobody actually ran the trivial "-k parse" test using 3.HEAD
> or the initial quoted strings code.
Or perhaps nobody ran such a test with non-trivial regular expressions
in squid.conf? I know I tested [very] early versions of the quoted
str
Looks like nobody actually ran the trivial "-k parse" test using 3.HEAD
or the initial quoted strings code.
Attached is a patch which adds a secondary form of undo for handling
incorrectly identified ConfigParser::FunctionNameToken elements. Instead
of aborting Squid on any non-function token
On 07/29/2013 03:02 AM, Kinkie wrote:
> On Sat, Jul 27, 2013 at 8:31 PM, Alex Rousskov wrote:
> 1a. Reserve total buffer capacity. Ensure exclusive buffer ownership.
>
> 1b. Reserve buffer space. Ensure exclusive buffer ownership.
>
> 2. Reserve N space b
I am building the new beta and it seems to configure and build nicely on
CentOS 6.4 x64 but only when building manually.
When I built it using the squid.spec that was being used with 3.3.8 I
started getting some SNMP problem.
output:
---
libtool: link: g++ -I/usr/include/libxml2 -Wall -Wpointer
On Sun, Jul 28, 2013 at 1:03 AM, Alex Rousskov
wrote:
> On 07/27/2013 02:57 PM, Kinkie wrote:
>> On Sat, Jul 27, 2013 at 10:32 PM, Alex Rousskov
>> wrote:
>>> On 07/27/2013 01:03 PM, Kinkie wrote:
On Sat, Jul 27, 2013 at 8:31 PM, Alex Rousskov wrote:
> On 07/27/2013 12:00 PM, Kinkie wrot
15 matches
Mail list logo