Yea its a different sort of monster from a RegEx. The performance is pretty bad in the engines I've used, I imagine the asm engine doesn't perform so well either. But for its purposes it works pretty well.

Hello Ozzy.
Pelles C standard library actually does not use PCRE. (At least the version that I have.) It comes with (a modified version of) Henry Spencer's regex library.
http://arglist.com/regex

Hello f0dder.
Nothing is wrong with PCRE. Ignore this thoughtless and stupid comment. What I really wanted to say is that you should also consider other libraries. As
tantrikwizard already mentioned you should choose the library that suits your and your potential users needs. Using PCRE has a lot of advantages, for
example, everbody familiar with PERL will feel right at home with your application. It also supports portability of regexes between your application and PERL.

vid wrote:

Unless anybody provides a counter-example, it is error free code.

The current implementation status of regcomp is as follows:

- leftmost longest match (returns start and end of a match)
- leftmost shortest match (returns start and end of a match)
- character classes
- case insensitivity
- backward searching
- minimum match length

The next step is adapting regexec.

I think I'll release the next version on 02/28/07.

By the way, does anybody of you have an idea of how to identify the longest string that must occur in every match? I've heard that grep is able to do that and
then uses a fast exact string matcher like quicksearch to speed up the search.

And when someone provides a counter-example, it miraculously changes to bee an erroneous code, without having a single byte altered?

Clearly, if somebody provides a counter-example then it actually has never been error-free code. Although I did not proved the code correct(yet), I'm very sure it is. Thus the claim.

No hurry.

FYI, xgrep 1.03 (DOS, 8086) is now available (soon to be officially part of FreeDOS?) w/ .ASM src. Hooray!

EDIT: Post #786 (via my P4, a so-called 786, heh).

I just saw it today!
Very impressive mrpink!

 o__=-
 )
(\
 /\  
    

Thanks!

hi there,

i've done some updates and extensions to the regex engine.

it now passes almost all tests in basic.dat from:

http://www2.research.att.com/~gsf/testregex/

code size is about 8.8k including the code needed for running
it as an egrep-like commandline tool.

if somebody is interested and has a real project to include it
or has an idea for its usage let me know.

mrpink, I'm interested in this project, i'm working on using this library as tinypy module for KolibriOS. Please, upload here your new version. Thx for great work!

hello XVilka, what is your project about? please tell me a little bit about it.
maybe you can share your source code and we can work together to find
the best solution how to integrate my code with yours. you might need
some additional stuff like support for cyrillic/russian character set and
other regex syntax than posix ere.

mrpink: i'm trying to implement system-wide module/lib for KolibriOS and tinypy http://redmine.kolibrios.org/projects/kolibrios/repository/show/programs/develop/tinypy

sorry but I still don't understand. do you need to call it from C? please
tell me a more about Your code

Sorry for big delay.
Yes. I need call it from C (or from fasm, if TinyPy will be rewritten on fasm). It is for implementing "re" module for tinypy. And of course, this library can be system-wide for KolibriOS, and for other its programs.

If it supports most of the syntax, it has long desired solution. I have long waited for such a project, but unfortunately before they had very limited support for syntax.

cool, writing coreutils in FASM?

i'm in

ps.:
REGEXP rulz

Hi all. I've updated the code, added some features and renamed the package.
Check it out.

Hi, mrpink.
I just downloaded your code. It is really impressive work. But I have some advices about your coding style:
1. Never use "fix" directive at all. It is provided for very specific tasks. The usual program should never use it at all.

2. Also, don't use "equ" to define numeric constants. Use "=" instead.

Actually in your code all numeric constants should be defined with "=". I don't know why you are using "fix" and "equ"???

Well, when I started this project in 2007 I thought it is best to use fix
for constants you don't want to be overridden accidentally as fasm would do with constants defined with equ.
What are those very specific usages of fix you're talking about? I just thought, they're there for defining constants you wouldn't want to be redefined somewhere.
Anyway, is there any harm done by using fix and equ the way I did?

And thanks for your appreciation. I really like your work too. Keep it up.

It is relative, but for example, these constants (because they are preprocessor constants) can't be used with Fresh IDE code completion, cross reference, and all code exploration tools.

Now, is that my bad coding style or a weakness of Fresh IDE?
Anyway, shouldn't be a problem to do a search and replace for all fixes and equs
Hope to see my code in one of your projects though