Re: gets() and "string" variable type
c.k.lester wrote:
>
> CChris wrote:
>
> > This and other extremely useful additional Eu types will resquire more
> > native
> > types included. This will be very difficult to do without a thorough
> > reexamination
> > of bit and test patterns, as discussed before. Adding them straight into
> > the
> > interpreter is probably impossible.
>
> Is it possible to get unicode functionality via an include file?
It depends on how much functionality you need.
If you only need to process files, and probably most devices, which are not to
be parsed by the interpreter, then yes. You keep reading bytes, it's how you
interpret them that changes, and you can do that in an include file. Likewise,
you preprocess your Unicode chars into bytes before basically outputting bytes.
If you want the interpreter to handle identifiers with Unicode chars in it, then
it's a different matter. I didn't think about what it would take to achieve that.
If you want to process stdin input which is done using Unicode, and not one byte
at a time, then an include file may not be enough. I don't have OS versions that
support Unicode installed, so I cannot even experiment with this. When the OS
reads on devices in an uniform way, like Windows does, the point may be moot.
Otherwise, I don't know.
I haven't used Tommy's Unicode Library, nor Aku's read/write CSV files library,
which relies on the latter. They are the only general tools currently listed in
the archive (there's also a lib by Greg Haberek, but it is Windows only), and may
give you a clearer idea of what can and cannot be done.
CChris
|
Not Categorized, Please Help
|
|
