On 11/7/07, Marco van de Voort <[EMAIL PROTECTED]> wrote:
> > I tried:
> > http://www.hotlinkfiles.com/files/526004_qpvr0/pcre-fpc.tar.gz
> >
> > Can't get it to work.
>
then try this: http://www.renatomancuso.com/software/dpcre/dpcre.htm
I've used the above wrapper in a news ticker application w
>
> But we don't have, and may never have, one that is as fast and
> bug-free as pcre and that is compatible with pcre. The user
> of a library doesn't care whether it's written in Pascal or C.
True. But if native, it isn't a library but linked into the main (static)
binary, with all deployment
> I tried:
> http://www.hotlinkfiles.com/files/526004_qpvr0/pcre-fpc.tar.gz
>
> Can't get it to work.
Doing a dumb header port is not that hard. If you can't do it, start making
tests, and I'll do it.
___
fpc-pascal maillist - fpc-pascal@lists.freepas
--- L <[EMAIL PROTECTED]> wrote:
> > >> Ok, now somebody has to fix the regexpr unit and accelerate it *g*
> > >
> > > The C program in the shootout uses pcre (Perl-compatible
> > > regular expressions). It would be very nice if FPC came
> > > with pcre.
> >
> > Well, that way we can never win
There is also:
http://www.renatomancuso.com/software/dpcre/dpcre.htm
(By the way, why all these people wrap PCRE in a class is beyond me. Object
oriented PCRE.. defeats the bloody purpose of regular expressions in the first
place - quick and dirty access to regexes must not be stored in a class.
> >> Ok, now somebody has to fix the regexpr unit and accelerate it *g*
> >
> > The C program in the shootout uses pcre (Perl-compatible
> > regular expressions). It would be very nice if FPC came
> > with pcre.
>
> Well, that way we can never win :) Anyways, I think having an libc
> independent
--- Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> S. Fisher schrieb:
> > --- Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> >
> >
> >> Ok, now somebody has to fix the regexpr unit and accelerate it *g*
> >
> > The C program in the shootout uses pcre (Perl-compatible
> > regular expressions). I
I tried:
http://www.hotlinkfiles.com/files/526004_qpvr0/pcre-fpc.tar.gz
Can't get it to work.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
> The C program in the shootout uses pcre (Perl-compatible
> regular expressions). It would be very nice if FPC came
> with pcre.
I am also looking to ship PCRE with Powtils too since TRegexp isn't the best in
all situations.
We wrapped Tregexp too:
http://z505.com/cgi-bin/powtils/docs/1.6/idx.c
> The compiler uses shortstrings internally, which are the fastest string
> type. Pchars are between ansistrings and strings, but offer the least
> comfort of all.
Also WordString or LongIntString would be as fast or faster than a 255
Bytestring..
But haven't implemented or supplied a patch yet ;
Daniël Mantione schrieb:
>
> Op Tue, 6 Nov 2007, schreef Florian Klaempfl:
>
>> S. Fisher schrieb:
>>> --- Florian Klaempfl <[EMAIL PROTECTED]> wrote:
>>>
>>>
Ok, now somebody has to fix the regexpr unit and accelerate it *g*
>>> The C program in the shootout uses pcre (Perl-compatible
>>> r
> Op Tue, 6 Nov 2007, schreef Florian Klaempfl:
> > S. Fisher schrieb:
> > > --- Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> > >
> > >> Ok, now somebody has to fix the regexpr unit and
> accelerate it *g*
>
> If we want to win we could build in compler support and
> compile the regu
Op Tue, 6 Nov 2007, schreef Florian Klaempfl:
> S. Fisher schrieb:
> > --- Florian Klaempfl <[EMAIL PROTECTED]> wrote:
> >
> >
> >> Ok, now somebody has to fix the regexpr unit and accelerate it *g*
> >
> > The C program in the shootout uses pcre (Perl-compatible
> > regular expressions). It
S. Fisher schrieb:
> --- Florian Klaempfl <[EMAIL PROTECTED]> wrote:
>
>
>> Ok, now somebody has to fix the regexpr unit and accelerate it *g*
>
> The C program in the shootout uses pcre (Perl-compatible
> regular expressions). It would be very nice if FPC came
> with pcre.
Well, that way we c
--- Florian Klaempfl <[EMAIL PROTECTED]> wrote:
>
> Ok, now somebody has to fix the regexpr unit and accelerate it *g*
The C program in the shootout uses pcre (Perl-compatible
regular expressions). It would be very nice if FPC came
with pcre.
_
> The compiler uses shortstrings internally, which are the fastest string
> type. Pchars are between ansistrings and strings, but offer the least
> comfort of all.
With the exception that not having a compiler flag to check
shorstrings' overflows make for for some tricky to debug problems ;-)
-Fl
Op Tue, 6 Nov 2007, schreef L:
> The funny thing I see is everyone recommending Pchars. Why not
> setlength/uniquestring? Still too slow?
Memory management, especially when you get reallocations, is expensive.
With case ansistrings can perform well. However, you do have to care, and
Pchars ca
L schrieb:
There has been a long discussion on the Shootout forums about it. Isaac
believes that it is more fair this way for languages that don't have all
benchmarks implemented. Now we simply have to make him retract all our
poor performing programs :)
>>> Exactly. A not very
> > > There has been a long discussion on the Shootout forums about it. Isaac
> > > believes that it is more fair this way for languages that don't have all
> > > benchmarks implemented. Now we simply have to make him retract all our
> > > poor performing programs :)
> >
> > Exactly. A not very fa
On 11/6/07, S. Fisher <[EMAIL PROTECTED]> wrote:
>
> --- Dani�l Mantione <[EMAIL PROTECTED]> wrote:
>
> > > Is it true that a slow program has a worse effect on the shootout
> > > results than a missing program? That seems wrong to me.
> >
> > There has been a long discussion on the Shootout forum
20 matches
Mail list logo
