what -I- consider a bug in *cabe

[Kenneth Brody]

Quoting Fairlight (Fri, 1 Jun 2007 02:12:43 -0400):

> I written my subject line at least in a way that admits up front that
> it's my -opinion-, and this may not actually be a bug.

Noted.

[...]
> Working on Windows 2003 Server.  The uhm...console windows aren't really
> friendly about copy&paste of selected areas in terms of speed of use,
> since you have to throw it into mark mode and it acts a bit flaky, and
> do it one line at a time, etc.  So I basically just had two windows
> back to back and was transcribing some of my older, known-good code
> from one to the other far faster than I could copy and paste line by
> line.  Apparently slightly too fast...

You do know that you can F8/Save from one, and F8/Load in another,
don't you?

[...]
> Looking over the logic, I noticed something that obviously threw the
> calculation:
>
> TMin=mid(TDiff,"$","2")
>
> That was the segment that caused problems.  Obviously I was going for
> "4" in the starting position, and I did that whole, "I'm holding shift
[...]
> However, could someone please explain to me why having a string literal
> that is non-numeric in a mid positioning argument should not be a syntax
> error worthy of failing syntax check at save time?

Because it's not a syntax error, any more than SQRT("-1") is a syntax
error, or OPEN("c:\foo.txt","r") is a syntax error on Unix.

Are you passing a literal that is probably not what you meant?  Yes.
Is it invalid syntax?  No.

[...]

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