[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why are byte ports "ports" as such?

This page is part of the web mail archives of SRFI 91 from before July 7th, 2015. The new archives for SRFI 91 contain all messages, not just those from before July 7th, 2015.

Thomas Bushnell BSG wrote:
Per Bothner <per@bothner.com> writes:

You're contradicting yourself: I asked about a use-case for *character*
as a separate *data type*.

Text editors.

You need keyboard *events*, for input, but they're obviously quite
different from characters.  (They have modifier bits, plus maybe
separate up/down events.)

You need to store and modify text data in *buffers*, but there is no
need for characters as a separate data type.  You do need functions to
"move to the next character/word/line/paragraph", but again these work
in characters in a buffer, not individual characters.

You need be able to display the text, which involves searching for
glyphs in fonts, possibly performing kerning, line-breaking, etc.
Again, a character data type will probably be either too high-level
or too low-level. You certainly don't want to have it built-in to
your programming language, but into your display software.
	--Per Bothner
per@bothner.com   http://per.bothner.com/