Problem with INSTR()

[Kenneth Brody]

Quoting John Esak (Wed, 15 Feb 2006 13:50:01 -0500):
[...]
> >     If:  "l" eq "L"
> >   Then:  mesgbox "'l' and 'L' are the same!"
> >
> > :-)
>
> No, no, no,.... (at the risk of sounding like the bit in Tron... :-))
> Sorry, but that is a completely irrational analogy. What I am saying
> (very clearly) is that the following would not get the desired results
> from your point of view...
>
>     if:  l eq chr("76")
>   then: show "Ken is right, John is wrong! :-)";  end
>     if:
>    then: show "John is right! :-)  -- doesn't happen often, but even a
> blind squirrel gets the nut sometimes."

Well, assuming that you meant to put quotes around the lowercase "l"
on the first line, you will see that the first "if" is true, and the
"Ken is right..." message will be displayed.

I guess it depends on your definition of "the desired results".  :-)

> Truly, I believe if someone specifies a *particular* character with the
> use of chr(), filePro should respect that.

There is no difference between "L" and CHR("76").

> It does *everywhere* else I have tried, and I just tried about 10
> different things. Why should this INSTR() function be any different?

Can you give me a specific example in filePro where lowercase "l" and
capital "L" are not the same?  (Excluding filenames on a system which
is case-significant, of course.)

> Besides, it certainly would give the INSTR() function a lot more depth.
>
> So what would be wrong with PFINSTRWORKSLIKEJOHNWANTSITTO=ON  ??
>
> and keep the default OFF if you must. :-)

Why not just make all of filePro case-significant?  Why should INSTR()
be an exception to the rule?

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com