Thread: [Echelog-devel] New type: regex

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Hi,

What about create a new data type: 'REGEX', that can be used in
filter module?

Benoit

-- 
Benoit DOLEZ
GSM: +33 6 21 05 91 69                mailto:bd...@an...

On =DAt, 2003-02-18 at 21:27, Benoit DOLEZ wrote:
> Hi,
>=20
> What about create a new data type: 'REGEX', that can be used in
> filter module?
>=20
> Benoit
>=20

Echelog types are designed primarily for serialization into messages.
This doesn't seem to be the case.

You can check the attribute type for varchar,... (by is_compatible(attr)
for example) and perform any special operation you'd like to (like
regmatch to a compiled regular expression).

More generally, maybe attributes could be enhanced to handle regexp
comparisons but it'd need a precisely defined behaviour for each type --
how would that look like?

Kamil

Kamil Toman wrote:
> On =DAt, 2003-02-18 at 21:27, Benoit DOLEZ wrote:
>=20
>>Hi,
>>
>>What about create a new data type: 'REGEX', that can be used in
>>filter module?
>>
>>Benoit
>>
>=20
>=20
> Echelog types are designed primarily for serialization into messages.
> This doesn't seem to be the case.

Ok, you're right. My problem was to not compile regex for each line.
I move the compilation in the constructor and execute it in the
test_chunk function and it seems that it is working :-)

It is not a big patch but it may be useful.

About it, I'm not expert in C++ developement, how can I say
that tFilterCondRE::is_invalid() work like tFilterCondSS::is_invalid()?

>=20
> You can check the attribute type for varchar,... (by is_compatible(attr=
)
> for example) and perform any special operation you'd like to (like
> regmatch to a compiled regular expression).
>=20
Thanks,

Benoit

> More generally, maybe attributes could be enhanced to handle regexp
> comparisons but it'd need a precisely defined behaviour for each type -=
-
> how would that look like?
>=20
> Kamil
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Echelog-devel mailing list
> Ech...@li...
> https://lists.sourceforge.net/lists/listinfo/echelog-devel
>=20
>=20

--=20
Benoit DOLEZ
GSM: +33 6 21 05 91 69                mailto:bd...@an...

On St, 2003-02-19 at 00:30, Benoit DOLEZ wrote:
> > Echelog types are designed primarily for serialization into messages.
> > This doesn't seem to be the case.
> 
> Ok, you're right. My problem was to not compile regex for each line.
> I move the compilation in the constructor and execute it in the
> test_chunk function and it seems that it is working :-)
> 
> It is not a big patch but it may be useful.
> 
> About it, I'm not expert in C++ developement, how can I say
> that tFilterCondRE::is_invalid() work like tFilterCondSS::is_invalid()?

I've modified the patch, so tFilterCondRE is based on tFilterCondSS and
as such it inherits is_invalid routine.

The suggested feature (matching regular expressions) is now included in
CVS.

Kamil

> 
> > 
> > You can check the attribute type for varchar,... (by is_compatible(attr)
> > for example) and perform any special operation you'd like to (like
> > regmatch to a compiled regular expression).
> > 
> Thanks,
> Benoit