At 1:10 PM -0400 3/29/08, James Sentman wrote:
>I understand and even acknowledge the necessity of
>text encoding, but despise is not too strong a word for how I feel
>towards the implementation we're using.
I actually like RB's Text Encoding support. It does almost everything
for you automatically, AS LONG AS THERE'S A CORRECT TEXT ENCODING
ASSIGNED TO EACH STRING. You're at risk of getting a string without a
text encoding whenever you get a string from outside your program. eg
>from a file, socket, serial, database etc.
And you also get a string without an encoding from functions that
return binary data like MD5. Which is OK, except that RB will still
treat them as text without complaining. IMHO That's a major oversight.
RB should raise an exception if you perform a text function on a
string that doesn't have a text encoding. If you'd like RB to help
debug your latent text encoding issues sign onto these FRs.
Text operations on strings with no encoding should Raise Exception
http://www.realsoftware.com/feedback/viewreport.php?reportid=rcvdscun
Debugger should signal strings of unknown encoding
http://www.realsoftware.com/feedback/viewreport.php?reportid=rbsbzeyc
Regards,
Joe Huber
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|