It's 2017 now and we have WBin, WChr, WHex, WOct, WString, WSpace, WStr
but from my point of view we need WInkey WInput also.
What do you think about it ?
Joshy
Do we need WInkey() / WInput this days ?
-
- Posts: 8586
- Joined: May 28, 2005 3:28
- Contact:
Re: Do we need WInkey() / WInput this days ?
I basically agree, but I think Unicode support needs to be improved in general and this needs a holistic design to be integrated well without breaking code - if possible. Adding unicode support to the runtime method by method may impose problems later.
On the other hand some unicode support is already in FB and many unicode-specific functions were already added, so maybe that should just be continued.
On the other hand some unicode support is already in FB and many unicode-specific functions were already added, so maybe that should just be continued.
-
- Posts: 8586
- Joined: May 28, 2005 3:28
- Contact:
Re: Do we need WInkey() / WInput this days ?
2021 BUMP :-(
Re: Do we need WInkey() / WInput this days ?
Google finds 353 hits for site:freebasic.net define unicode problem
It is a can of worms. Personally, I detest the automatism that comes with #define unicode. It can cause lots of problems. I prefer things like Print "This is Ansi" vs wPrint "This is Unicode"
It is a can of worms. Personally, I detest the automatism that comes with #define unicode. It can cause lots of problems. I prefer things like Print "This is Ansi" vs wPrint "This is Unicode"