Support for Ascii compilation ends after the next LTS cycle
Re: Support for Ascii compilation ends after the next LTS cy
SpiderBasic just compiles to Javascript, so everything is done at browser level.
I think the file(s) output are UTF-8, but what the browser does with it is another question entirely.
I think the file(s) output are UTF-8, but what the browser does with it is another question entirely.
- the.weavster
- Addict
- Posts: 1537
- Joined: Thu Jul 03, 2003 6:53 pm
- Location: England
Re: Support for Ascii compilation ends after the next LTS cy
But I think the default encoding of an XMLHttpRequest object is UTF8 unless a header is included with the request to state otherwise, isn't it? As with PB it's the communication with external sources where you have to pay attention to encodings.Foz wrote:SpiderBasic just compiles to Javascript, so everything is done at browser level.
I think the file(s) output are UTF-8, but what the browser does with it is another question entirely.
-
- Addict
- Posts: 4527
- Joined: Thu Jun 07, 2007 3:25 pm
- Location: Berlin, Germany
Re: Support for Ascii compilation ends after the next LTS cy
I just recalled idle's ModXString contribution, which can be very useful especially in the light of this announcement.
Re: Support for Ascii compilation ends after the next LTS cy
I don't recall this being asked, but what will happen with, for example, Cipher functions, that explicitly need to be compiled in ASCII mode now.
http://www.purebasic.com/documentation/ ... er.pb.html
http://www.purebasic.com/documentation/ ... er.pb.html
- Mindphazer
- Enthusiast
- Posts: 346
- Joined: Mon Sep 10, 2012 10:41 am
- Location: Savoie
Re: Support for Ascii compilation ends after the next LTS cy
Odd logic againmarroh wrote: Odd logic, i need the feature to build ASCII exe, this is fact for me. Pointless to to discuss it, that you and other should accept.
If you don't want anyone to discuss about the message you posted, then why did you post it ??
MacBook Pro 14" M1 Pro - 16 Gb - MacOS 14 - Iphone 15 Pro Max - iPad at home
...and unfortunately... Windows at work...
...and unfortunately... Windows at work...
Re: Support for Ascii compilation ends after the next LTS cy
It has been asked on the previous page. According to the PureBasic team only the examples need to be updated.bbanelli wrote:I don't recall this being asked, but what will happen with, for example, Cipher functions, that explicitly need to be compiled in ASCII mode now.
If any of you native English speakers have any suggestions for the above text, please let me know (via PM). Thanks!
-
- Addict
- Posts: 4527
- Joined: Thu Jun 07, 2007 3:25 pm
- Location: Berlin, Germany
Re: Support for Ascii compilation ends after the next LTS cy
First general forum rule:c4s wrote:It has been asked on the previous page.
Avoid reading threads. Better just write to them.
Particularly don't read the thread to which you are writing.
Re: Support for Ascii compilation ends after the next LTS cy
Well, NOW I can see it.c4s wrote:It has been asked on the previous page. According to the PureBasic team only the examples need to be updated.bbanelli wrote:I don't recall this being asked, but what will happen with, for example, Cipher functions, that explicitly need to be compiled in ASCII mode now.
Thanks and sorry for unnecessary question.
Re: Support for Ascii compilation ends after the next LTS cy
+ 280569792841Shield wrote:I mentioned that it might make sense to add a special ASCII compatibility library,
basically a simplified version of the string library that allows us to apply basic operations
on "ASCII memory".
Re: Support for Ascii compilation ends after the next LTS cy
Which is silly since that would require a ASCII compatibility library with a matching function for all string related PB functions.es_91 wrote:+ 280569792841Shield wrote:I mentioned that it might make sense to add a special ASCII compatibility library,
basically a simplified version of the string library that allows us to apply basic operations
on "ASCII memory".
And there is no such thing as ASCII memory.
ASCII are bytes with values from 0-127, although when mosty say ASCII they mean Latin-1/ISO 8859-1 (or variants) which uses the full 0-255 range.
AFAIK there are no plans to get rid of .a or .Ascii
And if needed the PeekS and PokeS functions will be tweaked/improved and I think Fred (or Freak) stated that one or two functions would be added to make it very easy to convert a Ascii string to native and from native to Ascii.
The way you would do Ascii string comparisons is that you would fetch the ascii data use the function to turn it to a native string and then compare that.
Unless you do really weird things there is no need to change anything else.
Though if you currently use .b or .a in your loops if comparing individual you should change that to be .c instead to make life a little easier down the road.
Maybe Fred/Freak/Somebody else will make a few mini-tutorials with tips'n'tricks and post those on the blog so people can tweak/fix their code over the next few months.
As to those heralding the virtues of UTF8, I agree, but sadly Windows uses 16bit "characters" and not 8bit as UTF8 does, also just because the characters are 16 and 8 does not mean they are consistently that, since they are unicode they may be extended a d thus a character may span multiple "characters".
One of the cool things with UTF8 is that it's (real-)Ascii compatible (i.e. the first 0-127 range is identical, though 128-255 is not) and that it's endian neutral.
I use UTF8 for transmitting text for storing/reading etc.
I let PureBasic convert UTF8 strings to a native string and then I do character/string stuff using native strings.
And PB programmers should start to migrate their code to do the same.
Re: Support for Ascii compilation ends after the next LTS cy
No problem. All of my programs have the option "Create unicode executable" checked. Working smoothly.freak wrote:we decided to remove the ability to compile in ascii mode
At the rare points where Ascii is needed, I am using the flag #PB_Ascii.
- Windows 11 Home 64-bit
- PureBasic 6.10 LTS (x64)
- 64 Gb RAM
- 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz
- 5K monitor with DPI @ 200%
- PureBasic 6.10 LTS (x64)
- 64 Gb RAM
- 13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz
- 5K monitor with DPI @ 200%
- FihmpenRouk
- User
- Posts: 27
- Joined: Mon May 08, 2006 2:27 pm
Re: Support for Ascii compilation ends after the next LTS cy
Great news that I havn't seen until now (not here much).
Ascii is an old, old fart and it's time for it to finally conform to modern techs.
Actually I don't understand why there should be a delay in dumping ascii just because some peps haven't used the since-ages-possibility to use unicode.
*If* I absolutely have to have the support for ascii, I can always use an older version of PureBasic.
Development should never be stopped by slow adapters. They can use the older versions.
Keep up the good work, developers!
When will internet upgrade to skip support for whiners and reactionaries (back pullers in my language)?
It's not my intention to offend any of you guys, but if you're here I guess it's because you're interested in technology. Life is limited. Let the development of technology run as fast as it can by not having to much overhead, so we can experience as much as possible in our short lifetimes - that's my point.
(for You who find bugs - pinpoint them so the programmers can find them fast instead of wasting time to cry about bugs - win win in all directions - just saying)
Ascii is an old, old fart and it's time for it to finally conform to modern techs.
Actually I don't understand why there should be a delay in dumping ascii just because some peps haven't used the since-ages-possibility to use unicode.
*If* I absolutely have to have the support for ascii, I can always use an older version of PureBasic.
Development should never be stopped by slow adapters. They can use the older versions.
Keep up the good work, developers!
When will internet upgrade to skip support for whiners and reactionaries (back pullers in my language)?
It's not my intention to offend any of you guys, but if you're here I guess it's because you're interested in technology. Life is limited. Let the development of technology run as fast as it can by not having to much overhead, so we can experience as much as possible in our short lifetimes - that's my point.
(for You who find bugs - pinpoint them so the programmers can find them fast instead of wasting time to cry about bugs - win win in all directions - just saying)
PureBasic occasionally since 2000 - when hacks are to be done.
Re: Support for Ascii compilation ends after the next LTS cy
Hello there. IMHO, technology should be for everyone, be they whiners or boasters.FihmpenRouk wrote:Development should never be stopped by slow adapters...
When will internet upgrade to skip support for whiners...
For those who might feel hampered by the slow pace or progress of any one technology, there's no shortage of cutting-edge technologies to adopt.
No need to whine.
Just saying.
Texas Instruments TI-99/4A Home Computer: the first home computer with a 16bit processor, crammed into an 8bit architecture. Great hardware - Poor design - Wonderful BASIC engine. And it could talk too! Please visit my YouTube Channel
Re: Support for Ascii compilation ends after the next LTS cy
5.40 LTS is out. So i guess this is the last LTS to include ASCII.
I allready transitioned to unicode. Since this announcement i made all my new project unicode projects.
However for file formats and network protocols i am not using PB's UCS-2 or UTF-16 (whatever it may be). I am using UTF-8, which PB supports by using the UTF-8 flag on reading and writing commands.
The only inconvenience is that UTF is a variable length format, which makes some tasks a bit more complicated. To make file formats and especially network protocols secure, we need to take length in characters and length in bytes into consideration. Very important to check if buffers are big enough, etc.
Other than that i realy like it.
Would be even better if PB would use UTF-16 internaly instead of UCS-2.
I allready transitioned to unicode. Since this announcement i made all my new project unicode projects.
However for file formats and network protocols i am not using PB's UCS-2 or UTF-16 (whatever it may be). I am using UTF-8, which PB supports by using the UTF-8 flag on reading and writing commands.
The only inconvenience is that UTF is a variable length format, which makes some tasks a bit more complicated. To make file formats and especially network protocols secure, we need to take length in characters and length in bytes into consideration. Very important to check if buffers are big enough, etc.
Other than that i realy like it.
Would be even better if PB would use UTF-16 internaly instead of UCS-2.
Re: Support for Ascii compilation ends after the next LTS cy
Windows uses UTF-16 internal for API calls, so I thought PB uses also UTF-16? Am I wrong?Thorium wrote:Would be even better if PB would use UTF-16 internaly instead of UCS-2.