Hi, 2010/2/15 m...@watty <[email protected]>
> > > On Feb 14, 6:33 pm, Joep Suijs <[email protected]> wrote: > . > > It would be easy to add support for zero-terminated strings in > > print.jal though. On the other hand I would advice all string routines > > also handle strings without termination. > > > > Joep > > Yes. I agree. Relying on zero Termination is the greatest evil of C, C+ > +, Linux, OS X and Windows. > Looks like a shared evil :) > > I don't think we want VB6 BSTR nor Unicode. If 16bit characters/ > Unicode is ever needed that should be a separate Unicode library. For > 99.9% of PIC applications UNICODE/16bit is a huge waste. > I don't know much about VB strings, but Unicode seems way out of scope for PICs. More, this isn't an encoding on its own, Unicode is a way to have "abtracts" representation of chars, it becomes "concrete" with encodings, like UTF-8, UTF-16, etc... Maybe there could be support for some encodings, but as you say, looks like a huge waste (and everybody's using ASCII, right ? :)) > > I think packedBCD, Characters and Strings should be in the same > library as they are very related, > What are packedBCD ? Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
