Posté le 22/01/2020 21:53
Planète Casio v4.3 © créé par Neuronix et Muelsaco 2004 - 2024 | Il y a 84 connectés | Nous contacter | Qui sommes-nous ? | Licences et remerciements
Planète Casio est un site communautaire non affilié à Casio. Toute reproduction de Planète Casio, même partielle, est interdite.
Les programmes et autres publications présentes sur Planète Casio restent la propriété de leurs auteurs et peuvent être soumis à des licences ou copyrights.
CASIO est une marque déposée par CASIO Computer Co., Ltd
Citer : Posté le 22/01/2020 22:51 | #
Les strings sont physiquement limitées à 256 octets. À moins que C.Basic remonte cette limitation, tu ne pourra pas en mettre plus dedans.
Citer : Posté le 23/01/2020 03:14 | #
In C.Basic, the string variables can be extended with the following syntax.
n:maximam number of string variables.
m:maximam number of string characters.
Overclocking utilitaire Ftune/Ptune2/Ptune3 est également disponible.
Si vous avez des questions ou un rapport de bogue, n'hésitez pas à me le faire savoir.
Citer : Posté le 23/01/2020 08:40 | #
I think C.Basic does a great job of extending Casio Basic limitations, but sometimes I feel the change is half-hearted. Why not go all the way and:
• Make the Str array a map where any identifier can be used (eg. Str 10000)?
• Make String sizes dynamic up to the available size of the heap/RAM?
It kinda surprises me because your approach needs syntax extensions and manual directives. The semantics of Casio Basic already depend too much on the syntax (eg. you cannot say "Str A" with "A=1" and get "Str 1"). Why did you choose this direction? :o
Citer : Posté le 23/01/2020 12:13 | #
Thanks for the positive suggestions.
I must admit that there is some problem that needs to be solved about the implementation of strings.
At first, for compatibility with Basic Casio, I thought it was enough to handle only 255 characters.
For compatibility with Basic Casio, processing of multi-byte character is necessary,
but since it is a fairly heavy processing, the longer the strings, the greater the decrease in speed.
And the strings function processing has 10 levels of stack.
For that purpose, fixed-size arrays determined from the beginning were used for the strings.
I think it is possible to adjust them and assign them dynamically.
However, this is accompanied by considerable implementation changes, which is why the specifications can not change for now.
Dynamic string processing is expensive,
I'm thinking of incorporating C functions for processing large strings.
By the way, "Str. A" syntax is possible in C.Basic.
Overclocking utilitaire Ftune/Ptune2/Ptune3 est également disponible.
Si vous avez des questions ou un rapport de bogue, n'hésitez pas à me le faire savoir.
Citer : Posté le 23/01/2020 14:45 | #
By the way, "Str. A" syntax is possible in C.Basic.
And you know, this is the absolute superiority of C.Basic on Casio Basic. It is a fast-evolving language not limited by the meaningless syntax and semantics of the old Basic.
I tend to think that most people use C.Basic by intuition and do not necessarily look at all the details of the language (which I did once in detail when I translated the manual). The extensions are somehow well-hidden. I would suggest to exploit "invisible" extensions such as the number and size of lists, strings, and the places where you are allowed to use an expression to substitute a constant value, which are intuitive, without restraint.
Anyway, thanks for considering my remarks.