If somebody says shut up….that is clear violating the form of communication we should have. Second: I wrote about the problems with this article and that the headline isn’t the correct way to describe. So following to your logic somebody can post something what is in this form not correct and nobody can complain while that’s off topic? No. That’s nothing I will accept.
Really, I’m on the verge of telling you to shut up, too. Keeping things on topic is part of the community rules as well.
https://ifnotnil.com/faq#keep-tidy
Make the effort to put things in the right place, so that we can spend more time discussing and less cleaning up. So:
- Don’t start a topic in the wrong category.
- Don’t cross-post the same thing in multiple topics.
- Don’t post no-content replies.
- Don’t divert a topic by changing it midstream.
All you ever do is bible-thump Java with excessive and repetitive walls of text. It’s quite tiresome.
4 Likes
Sorry for the Off-Topic:
Ignore feature works great, just go to your profile → Preferences → Users and add one or more users to your Ignore list.
The forum will hide the replies/posts but allow you to see them if you want (need to click on view):
2 Likes
Not needed. Leaving here.
LOL, I didn’t even see the traffic – I ignored them ages ago. 
Why PureBasic chose to use UCS2 strings instead of UTF-8? I think UTF-8 makes more sense today.
It uses USC2 internally due to native compatibility with Windows, but automatically reads/writes UTF8, so you more or less never notice this. In fact, I had to look this up because I’ve never had any issue and was assuming it was just UTF-8 throughout. Unicode
It also offers string handling functions and flags to work across UTF-8, ASCII, and PB_Unicode, which is apparently UCS. I’ve actually found this easier than dealing with Encodings in Xojo, though clearly it doesn’t support an arbitrary encoding.
That said, the next version (6.4alpha) was just announced yesterday, and Fred discussed the rewrite of the string manager toward increasing performance. It’s supposed to be “99%” backward compatible, so I expect that this same relationship with UTF-8 will continue.