Re: SD: Re: DHOS Shell
[Prev][Next][Index][Thread]
Re: SD: Re: DHOS Shell
<snip>
>text isn't a standard... windows/dos uses <cr><lf> to end a line while
Text is a standard if you choose to code your text in the standard.
(Unicode, the new 32-bit standard for characters is the same on any
platform. See http://www.unicode.org for more information.)
>un*x uses only <cr> (<cr> = carriage return, <lf> = line feed)
The line feed and carriage return will be seen as whitespace. I'm defining
whitespace the same way that C++ defines whitespace.
>ascii and ebdic (sp?) are different standards for text... ebdic is a
>proprietary IBM text format... and the extended ascii character set is
>different on most systems (ie. MacOS vs. Win/dos)... the DHOS team would
>have to decide on a "standard" for text.
Enter Unicode.
I have been discussing this idea with Kaus. I'm going to write up the first
draft of the idea and then send it out to everyone. This should explain
everything that the new shell scripting language will preform but yet,
anyone will be able to write there own shell.
~~ Dan ~~
>
>dan wrote:
>>
><snip>
>>
>> 4) Text is smaller, can be transmitted over the Internet without error
and
>> is one of the only true standards left.
>>
><snip>
>> I hope this brief email brought some of my ideas to the table. XML/SGML
and
>> stylesheets are very complex and take months to master. It would be hard
for
>> me to explain every aspect of the shell language that I'm thinking of.
>>
>> I think that Matt had a great idea for using text strings to hold the
shell
>> layout. This would be great to use. I would be more than happy to lead
this
>> aspect if no one objected to using XML/SGML just due to the power of the
>> language.
>>
>> Comments and Suggestions are Welcome.
>> ~~ Dan Hable ~~
>>
>> -----Original Message-----
><snip>
>--
>They who fight with monsters must take care lest they become a monster.
>For
>if you gaze too long into the Abyss, the Abyss gazes back into you.