However, the above thread has shown that people wish for a longer transition period, and we would like to honor this wish. What are your thoughts about it ? Is it a deal breaker for you ?Įdit: before freaking out, we are just talking about removing the "unicode switch", not all ascii related operations !Īs Fred has explained here, supporting both the creation of ascii and unicode executables in the compiler is becoming a burden and we would like to end support for ascii compilation in order to streamline the library code and make it easier to maintain the PureBasic package in the future. We would like to do it for the 5.40 version. No more unicode switch, so it's easier when sharing code source on the forum, or when developping an user lib (everybody is unicode) Faster building time, less code in our source tree, makefiles much shorter We plan to provide 2 new functions, to ease things a bit: So if you used somewhere in your code, change are high it won't work anymore (if dealing which an API for example) All strings in PB will be handled as UCS2 (16-bit) strings internally. If not, then you can enable it and test it.
#Purebasic 5.40 software
Basically, if your software runs with the "unicode" swith ON, nothing will change, you can skip the following text.
Also, ASCII is an old tech and is condamned to disappear sooner or later, as unicode can handle it as well. Still supporting ASCII is a big work for us, as we need to provide duplicate fonctions when dealing with strings, which can leads to more bugs. That means than every OS (Windows XP+, OS X 10.5+, Linux) now supports unicode natively, so we discussed with Timo the opportunity for us to remove ASCII support from PB and provide an unicode only compiler. Since PB 5.30, the minimum Windows OS to run PureBasic is Windows XP.
0 kommentar(er)
