Bob Jamison wrote:
to a much cleaner URI ---to--->istream and URI ---to--->ostream
...with built-in support for localization, it would make things a LOT easier.
Ew ew ew.
There is also a pair of iostream implementations I found, that provide printf() and scanf() style formatting, to alleviate the pain of conversion somewhat.
Eww ew ew ew!
This would be a lot like Java's "java.io.*" heirarchy, putting streams, files, URI/URL's and paths into one place.
Kinda.
Any thoughts, opinions? This is just something I have been thinking about recently.
Well, as you can tell, I do have a few opinions. :-)
Seriously, though, there are some issues I have with things. Some is the 'built-in' localization in streams. Generally good for the first 80% of a project, but breaks down in the final 20%. Same with printf.
One huge beef I have with the latest Java is their introduction of printf, instead of sticking with the nice i18n stuff that Taligent figured out. Sure, it will lure in a few more C programmers, but things break down in the long run.
Soo... switching to some higher-level classes and possibly streams is good. Overloading operations may not be, and 'automatic' or 'transparent' localization is generally something I try to avoid at all costs.