Re: Two Scary Mac Bugs (just in time for Halloween)

[Keith DeLong <lists@redcort.com>]

> Agreed that results should be consistent between platforms
> But you should also not count on an int32 key grabbing something
> inserted using an int64 key and vice versa
> 
> Strings have this behavior because of encoding (try Hello as ASCII and
> Hello as UTF16)
> Int32 / Int64 may behave the same

Hey Norman,
While I agree it's easy to get into trouble because of legacy Integer
support and lousy string conversion support in RB.

We have a ton of legacy code that uses dim Integer instead of explicit
Int32 of Int64 declarations. RB needs to be cooperative to the legacy code
or get rid of Integer all together and force the pain ;-)

And while String.CLong has been a big help after years with Integer =
String.Val as the only way to convert strings to number (via an awful
implicit double to integer conversion.)

I'll plead again for the day when strings get some love so they have the
same consistency Variants have received the past few years:

String.DoubleValue
String.Int64Value
String.Int32Value
String.CurrencyValue
String.DateValue 
Etc.

(Yes, I've filed a feedback on this long ago :-). I use lots of listboxes
and dictionaries so smooth string to key conversions are really important to
me. 

Keith DeLong



_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>