Gobo Eiffel Project

Majkel,

Sorry again for not answering earlier.

> my unicode classes also use the unicode database
> (ftp://ftp.unicode.org/Public/3.1-Update/UnicodeData-3.1.0.txt) to
> generate the tables containing information about the character's
> category, its mapping to lowercase, uppercase, titlecase, its bidi etc.
> from time to time some properties change and new characters are added.
> 
> currently, the tool is able to generate the 5 class UC_CTYPE_*.e. the
> tool i have written in eiffel (currently it's called uc_table_maker)
> could go to a tool directory to allow users to generate the tables
> itself. it does not belong into the $GOBO/library/kernel/unicode
> directory.

I'm not sure whether we should put the source code of
your tool in $GOBO/src/ or in a new directory in 
$GOBO/work. So far the $GOBO/work directory contains
files/scripts which are used to build a development
or delivery package of Gobo. On the other hand 
$GOBO/src currently contains the source code of tools
which can be useful for Eiffel programmers other than
those who are members of the Gobo development team.
So since your 'uc_table_maker' tool is used to generate
files within the Gobo library and are not meant to
be used outside of the Gobo package, $GOBO/work is
probably the way to go. What about:

   $GOBO/work/tool/uc_table_maker/*

? But I'm not too sure about the name of your tool.
Since it is supposed to generate UC_CTYPE_* classes,
what about renaming it as 'uc_ctype_maker' (this
name was suggested to me by Franck Arnaud) and puting
it into $GOBO/work/tool/uc_ctype_maker/ ?

Does anyone have a better idea for the name of this
tool and where to put it in the Gobo CVS repository?

-- 
Eric Bezault
mailto:ericb@...
http://www.gobosoft.com

Eric Bezault wrote:
> Eric Bezault wrote:
> >
> > I'm currently working on the following additions to
> > Gobo: KL_INPUT_STREAM, KL_INPUT_FILE, KL_OUTPUT_STREAM,
> > KL_OUTPUT_FILE, KL_FILE_SYSTEM, KL_DIRECTORY, ...
> > I hope that this will address your needs.
> 
> These classes (and more) are now available from the Gobo
> CVS repository. For details, see my message at:

Eric,

as far as i can see, these classes (KL_INPUT_FILE) support reading files
line by line. you are assuming, that lines are terminated by '%N' or
'%R%N'. this are the line endings for unix and ms-windows. but
mac-generated files end with '%R' i think. (i don't have access to or
work with the Mac, but some pdf-files i read had the line ending '%R').
so you should change the code to accept '%N', '%R%N', or '%R' as line
endings.

--
majkel.kretschmar@...