If I have to choose between "fast" or "ugly" then case sensitive being
fast and beautiful it is.
If I went with personal convenience and C# et al I would be running
windows and certainly wouldn't be contributing to Open Source.
Come up with a reasoned argument (other than personal convenience) th
So can we see light at the end of the tunnel? (hopefuly it's not the
light of an incoming train..). Have a nice weekend! P.
>
> I want a smart solution, not a fast and ugly one.
> And smart means
> really smart. And I take the time for it... I've
> got some ideas
> already...
>
> Matthias
Pito,
> I do understand the issue with comparing words and not single chars
> in you implementation, but tell me please - what is the major reason
> for your hardcore position of not wanting to have a switch for case
> sensitivity/insensitivity?
I want a smart solution, not a fast and ugly one. A
Matthias,
yes, sometimes I never give up..
I do understand the issue with comparing words and not single chars
in you implementation, but tell me please - what is the major reason
for your hardcore position of not wanting to have a switch for case
sensitivity/insensitivity? Pito
...
(besides that
Pito,
you never give, yea?
> the 4th is using a constant "casesensitive" for switching case
> sensitivity on/off. I've found that only "compare.4th" is using this
> constant (compares two strings). In C sources there is "comp_4th.c"
> which does mention sensitivness, but not using the constant. C
Hi Matthias,
the 4th is using a constant "casesensitive" for switching case
sensitivity on/off. I've found that only "compare.4th" is using this
constant (compares two strings). In C sources there is "comp_4th.c"
which does mention sensitivness, but not using the constant. Can
this somehow be used
