realbasic-nug
[Top] [All Lists]

Re: RB text encoding support

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: RB text encoding support
From: Joe Strout <joe at inspiringapps dot com>
Date: Sat, 29 Mar 2008 20:41:01 -0600
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <226027DE-9E67-4701-90AD-12E8F3383CF6 at rbclass dot com> <A652AB13-FCF7-4D95-B6B1-5EC6EC3E84DE at inspiringapps dot com> <3E14F3DA-1A0F-47A7-A23A-5561C8EFDFC3 at rbclass dot com> <A0720DC7-6E68-4825-B1E7-06FA772B07E7 at inspiringapps dot com> <A08DAFF0-4131-4C31-BE88-965126CC576F at rbclass dot com> <09004169-C758-401C-BF6E-6FB615336097 at rbclass dot com> <1BD9DBC6-83AA-42FF-912E-010229927261 at sentman dot com> <p06240800c4143a8c7b0d at [10 dot 0 dot 1 dot 8]>
On Mar 29, 2008, at 1:16 PM, Joe Huber wrote:

> RB should raise an exception if you perform a text function on a
> string that doesn't have a text encoding.

Yes, in 4.5 it was too soon to do that -- too many people's projects  
would have appeared to break.

But that was years ago now, and I agree, if you treat a string as  
undefined encoding as text, it's an error and should be signalled as  
such.

Best,
- Joe


--
Joe Strout
Inspiring Applications, Inc.
http://www.InspiringApps.com



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

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


<Prev in Thread] Current Thread [Next in Thread>