gobo-eiffel-develop — Development discussions

[gobo-eiffel-develop] EDP -- The Eiffel Developer's Project

[Howard T. <how...@di...>]

Hi all,

I have made a download available of the current state of my Eiffel IDE 
project, as a tar.bz2 archive of the source code of my development tree.

I have also provided executables for Linux and Windows, both 32-bit.

The 64-bit executable for Linux now works when compiled by edp+gcc, and the 
32-bit Linux code can also be compiled by EiffelStudio, or at least I have 
successfully done so once.

It is very much alpha status, and is certainly not yet a replacement for 
anything else, although I am starting to find it useful in it's code-browsing 
usage, with feedback about which classes within a class universe are part of 
the current system.

The WIN32 version compiles and links, albeit not yet using geant for the 
complete process. Although the SmartEiffel compiled version ran, I have made 
some major API changes since then between the Eiffel code and the supporting 
WIN32 glue code, so the current code may not.

When renamed as 'gec', the edp executable performs as 'gec' and is the version 
of 'gec' that I use to generate both Linux and Win32 C files for further 
processing. I may well need to provide a bootstrap process to simplify 
startup for working with the EDP project code.

The supplied directories 'edp' and 'tool' are intended to be located as 
subdirectories of $GOBO, with 'tool' provided primarily to show that some of 
the entries are symlinks into 'edp/tool/' and 'edp/library' containing 
modified classes needed for the adapted 'gec' functionality.

Note that the Eiffel code links directly with libX11 and libgdi32 and is 
therefore independent of any C/C++ GUI code on either platform, and that was 
one of my primary aims when starting out on this project.

The (minimal !) website is at http://ashford-ht.vm.bytemark.co.uk

Comments and criticism welcome ...

Regards,

Howard Thomson

--
"Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former." -- Albert Einstein 

Re: [gobo-eiffel-develop] svn:eol-style property not set

[Colin P. A. <co...@co...>]

>>>>> "Colin" == Colin Paul Adams <co...@co...> writes:

>>>>> "Eric" == Eric Bezault <er...@go...> writes:
    Eric> col...@us... wrote:

    >> gobo/trunk/test/xml/xslt/data/character_map2.out
    >>> gobo/trunk/test/xml/xslt/data/character_map4.out

    Eric> These files don't have the property svn:eol-style set.

    Colin> I don't know what to do about this. I tried making the
    Colin> results verbatim manifest strings. The tests then fail as
    Colin> the embedded CR characters (which show up as ^M in Emacs)
    Colin> are not being read from the verbatim string (using "{ }"
    Colin> delimiters) into the STRING object.

    Colin> (Eiffel Studio 6.0).

I reverted to using the output files for comparing test results.
I added the svn:needs-lock property to make them read-only (so you
will not be tempted to edit them on Windows - these are generated
output - that is I invoke gexslt on the test input files, and divert
standard output to the file. Then I inspect the output to check it is
correct).

I then set the svn:eol-style property to LF, combined with reading the
files as binary files, in a effort to avoid the different results problem.

Unfortunately, the two tests are still failing on Windows.
-- 
Colin Adams
Preston Lancashire

Re: [gobo-eiffel-develop] svn:eol-style property not set

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> col...@us... wrote:

    >> gobo/trunk/test/xml/xslt/data/character_map2.out
    >> gobo/trunk/test/xml/xslt/data/character_map4.out

    Eric> These files don't have the property svn:eol-style set.

I don't know what to do about this. I tried making the results
verbatim manifest strings. The tests then fail as the embedded CR
characters (which show up as ^M in Emacs) are not being read from the
verbatim string (using "{ }" delimiters) into the STRING object.

(Eiffel Studio 6.0).
-- 
Colin Adams
Preston Lancashire

Re: [gobo-eiffel-develop] svn:eol-style on *.xml

[Bernd S. <ber...@in...>]

On Fri, 12 Oct 2007 10:09:55 +0200, Eric Bezault <er...@go...>  
wrote:

> But I'm not sure it's a  good time to start a religious
> war on text editor...

Right, but we are all desperately waiting for you to get tired of your  
current editor and start developing GoboEdit :-)

Bernd

Re: [gobo-eiffel-develop] svn:eol-style on *.xml

[Eric B. <er...@go...>]

Berend de Boer wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
>>>>>> "Eric" == Eric Bezault <er...@go...> writes:
> 
>     Eric> But it is annoying when people on Windows want to edit these
>     Eric> files.  Sometimes they don't display nicely in Windows text
>     Eric> editors.
> 
> Still using notepad Eric :-)

No, or just sometimes just to view quickly a file.
On the other hand I'm not using an editor which inserts
spaces instead of tabs ;-)

But I'm not sure it's a  good time to start a religious
war on text editor...

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

Re: [gobo-eiffel-develop] svn:eol-style on *.xml

[Berend de B. <be...@po...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> But it is annoying when people on Windows want to edit these
    Eric> files.  Sometimes they don't display nicely in Windows text
    Eric> editors.

Still using notepad Eric :-)

- -- 
Cheers,

Berend de Boer


PS: This email has been digitally signed if you wonder what the strange
characters are that your email client displays.
PGP public key: http://www.pobox.com/~berend/berend-public-key.txt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFHDtOnIyuuaiRyjTYRAkZTAJ90XYzv7QgWV3Thk6AuuOgMU4rlyQCg5esm
P8xSbyk3lWqmz+XPDGI67d8=
=xbuI
-----END PGP SIGNATURE-----

Re: [gobo-eiffel-develop] svn:eol-style on *.xml

[Colin A. <col...@ho...>]

hh
> From: er...@go...

> > I also note that it shouldn't matter in this case, as XML parsers
> > are required to normalize line endings to a single line-feed.=20
>=20
> But it is annoying when people on Windows want to edit these files.
> Sometimes they don't display nicely in Windows text editors.

OK. That's a fair point.
=20
> > Update - if I try to do a propedit on the files, to add the svn:eol-sty=
le,=20
> > it warns me that they have a binary mime-type (it means application/xml=
).
>=20
> Yes, same for me. I guess you have to remove the mime-type property
> first. Then you can try to add it back after svn:eol-style has been
> added, although I doubt that it will work.

I don't intend to add it back.

I originally added the mime-type keyword allocations in my subversion confi=
g file when I was converting Goanna to use subversion. I carefully read up =
about subversion first, and realized what a good idea it was to annotate th=
e files with the content type.

But then I quickly discovered that in practise it isn't, as subversion won'=
t do text diffs on files when it considers the content type is not text (wh=
ich is all well and good, if it only had some knowledge about the standard =
types). I just haven't got round to removing it from my config files yet. I=
 will now.

_________________________________________________________________
The next generation of MSN Hotmail has arrived - Windows Live Hotmail
http://www.newhotmail.co.uk=

Re: [gobo-eiffel-develop] Gcc warnings when bootstraping

[Eric B. <er...@go...>]

Colin Paul Adams wrote:
> I just re-ran the bootstrap (gcc/ge) and I get the following warnings:
> 
> gexace.h:10631: warning: array GE_dts assumed to have one element
> gexace.h:10632: warning: array GE_dts assumed to have one element
> gexace.h:10631: warning: array GE_dts1 assumed to have one element
> gexace.h:10632: warning: array GE_dts2 assumed to have one element
> gexace.h:10631: warning: array GE_dts1 assumed to have one element
> gexace.h:10632: warning: array GE_dts2 assumed to have one element
> 
> I don't know if you can do anything about them, but it would be nice
> to have zero warnings.

It should be fixed now.

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

Re: [gobo-eiffel-develop] svn:eol-style on *.xml

[Eric B. <er...@go...>]

Colin Adams wrote:
> I can't work out why this wasn't applied to the two xml files. The svn:keywords was applied.
> 
> I also note that it shouldn't matter in this case, as XML parsers
> are required to normalize line endings to a single line-feed. 

But it is annoying when people on Windows want to edit these files.
Sometimes they don't display nicely in Windows text editors.

> Update - if I try to do a propedit on the files, to add the svn:eol-style, 
> it warns me that they have a binary mime-type (it means application/xml).

Yes, same for me. I guess you have to remove the mime-type property
first. Then you can try to add it back after svn:eol-style has been
added, although I doubt that it will work.

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

[gobo-eiffel-develop] svn:eol-style on *.xml

[Colin A. <col...@ho...>]

I can't work out why this wasn't applied to the two xml files. The svn:keyw=
ords was applied.

I also note that it shouldn't matter in this case, as XML parsers are requi=
red to normalize line endings to a single line-feed.=20

Update - if I try to do a propedit on the files, to add the svn:eol-style, =
it warns me that they have a binary mime-type (it means application/xml).

This is an annoying thing about subversion - it allows you to sensibly add =
mime-types, and then refuses to work if you do so.

_________________________________________________________________
The next generation of MSN Hotmail has arrived - Windows Live Hotmail
http://www.newhotmail.co.uk=

Re: [gobo-eiffel-develop] svn:eol-style property not set

[Colin A. <col...@ho...>]

> >     Eric> col...@us... wrote:
> >     >> Added Paths: ----------- gobo/trunk/doc/xml/serializers.xml
> >     >> gobo/trunk/doc/xml/xslt/xslt_serializer.xml
> >=20
> >     >> gobo/trunk/test/xml/xslt/data/character_map2.out
> >     >> gobo/trunk/test/xml/xslt/data/character_map4.out
> >=20
> >     Eric> These files don't have the property svn:eol-style set.
> >=20
> > I think subversion rejected it because the files themselves were
> > inconsistent with the styles.
>=20
> Even for the two .xml files in the doc directory?

I didn't have time to look at them. I'll take a look next weekend.

_________________________________________________________________
Feel like a local wherever you go.
http://www.backofmyhand.com=

Re: [gobo-eiffel-develop] svn:eol-style property not set

[Eric B. <er...@go...>]

Colin Paul Adams wrote:
>>>>>> "Eric" == Eric Bezault <er...@go...> writes:
> 
>     Eric> col...@us... wrote:
>     >> Added Paths: ----------- gobo/trunk/doc/xml/serializers.xml
>     >> gobo/trunk/doc/xml/xslt/xslt_serializer.xml
> 
>     >> gobo/trunk/test/xml/xslt/data/character_map2.out
>     >> gobo/trunk/test/xml/xslt/data/character_map4.out
> 
>     Eric> These files don't have the property svn:eol-style set.
> 
> I think subversion rejected it because the files themselves were
> inconsistent with the styles.

Even for the two .xml files in the doc directory?

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

Re: [gobo-eiffel-develop] svn:eol-style property not set

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> col...@us... wrote:
    >> Added Paths: ----------- gobo/trunk/doc/xml/serializers.xml
    >> gobo/trunk/doc/xml/xslt/xslt_serializer.xml

    >> gobo/trunk/test/xml/xslt/data/character_map2.out
    >> gobo/trunk/test/xml/xslt/data/character_map4.out

    Eric> These files don't have the property svn:eol-style set.

I think subversion rejected it because the files themselves were
inconsistent with the styles. And two test cases are failing on
Windows but not on Linux. I think it is for the same reason -
character maps are being used to produce non-well-formed XML, which
includes CR characters.

I'm not sure what to do about this yet - I will look into it next weekend.
-- 
Colin Adams
Preston Lancashire

[gobo-eiffel-develop] svn:eol-style property not set

[Eric B. <er...@go...>]

col...@us... wrote:
> Added Paths:
> -----------
>     gobo/trunk/doc/xml/serializers.xml
>     gobo/trunk/doc/xml/xslt/xslt_serializer.xml

>     gobo/trunk/test/xml/xslt/data/character_map2.out
>     gobo/trunk/test/xml/xslt/data/character_map4.out

These files don't have the property svn:eol-style set.

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

[gobo-eiffel-develop] Gcc warnings when bootstraping

[Colin P. A. <co...@co...>]

I just re-ran the bootstrap (gcc/ge) and I get the following warnings:

gexace.h:10631: warning: array GE_dts assumed to have one element
gexace.h:10632: warning: array GE_dts assumed to have one element
gexace.h:10631: warning: array GE_dts1 assumed to have one element
gexace.h:10632: warning: array GE_dts2 assumed to have one element
gexace.h:10631: warning: array GE_dts1 assumed to have one element
gexace.h:10632: warning: array GE_dts2 assumed to have one element

I don't know if you can do anything about them, but it would be nice
to have zero warnings.
-- 
Colin Adams
Preston Lancashire

[gobo-eiffel-develop] XM_FORMATTER

[Colin P. A. <co...@co...>]

I am puzzled as to why XM_RESOLVED_FORMATTER is marked as obsolete,
but XM_FORMATTER is not. I am writing documentation on the serializers
provided in gobo, and have just mentioned the latter. But there seems
to be an inconsistency.
-- 
Colin Adams
Preston Lancashire

Re: [gobo-eiffel-develop] Serializer example

[Eric B. <er...@go...>]

Colin Paul Adams wrote:
>>>>>> "Eric" == Eric Bezault <er...@go...> writes:
> 
>     Eric> Hi Colin, Would it be possible that you add a Readme.txt
>     Eric> file in your serializer example explaining what it is and
>     Eric> how to use it? All examples should come with a Readme file.
> 
> It's not really finished yet (although it is working), as I am still
> refactoring the XSLT serialization (and fixing bugs). I intend to
> provide documentation on the serializer as part of the XSLT
> documentation (although I will add a separate link to it from the main
> XML documentation page, to draw attention to it), and I will refer to
> the example in that, I think. 
> So the Readme.txt will probably just point to the documentation.

That's fine.

>     Eric> Also, it would be nice if you could update the test class
>     Eric> $GOBO/test/example/xml/xm_etest_serializer.e to provide some
>     Eric> input sample and check the output, as it is done in other
>     Eric> tests such as the one for the schematron or for the argument
>     Eric> library example.
> 
> What to test?  It's a general XML serializer, with many options
> affecting the way serialization is performed.

Test that this example does not crash when provided
a simple input. I've seen many Eiffel packages providing
examples which either didn't even compile or crashed
the first time they were executed. So the tests in
$GOBO/test/example are there to try to avoid that
embarrassing situation in the Gobo package.

> If it's just to check that the example compiles, then I could
> serialize <doc/> with options to specify that it comes out as <doc/>.

Why not, that's fine as long as we have a test that
compiles the example and executes it.

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

Re: [gobo-eiffel-develop] Serializer example

[Colin P. A. <co...@co...>]

>>>>> "Eric" == Eric Bezault <er...@go...> writes:

    Eric> Hi Colin, Would it be possible that you add a Readme.txt
    Eric> file in your serializer example explaining what it is and
    Eric> how to use it? All examples should come with a Readme file.

It's not really finished yet (although it is working), as I am still
refactoring the XSLT serialization (and fixing bugs). I intend to
provide documentation on the serializer as part of the XSLT
documentation (although I will add a separate link to it from the main
XML documentation page, to draw attention to it), and I will refer to
the example in that, I think. 
So the Readme.txt will probably just point to the documentation.

    Eric> Also, it would be nice if you could update the test class
    Eric> $GOBO/test/example/xml/xm_etest_serializer.e to provide some
    Eric> input sample and check the output, as it is done in other
    Eric> tests such as the one for the schematron or for the argument
    Eric> library example.

What to test? It's a general XML serializer, with many options
affecting the way serialization is performed.
If it's just to check that the example compiles, then I could
serialize <doc/> with options to specify that it comes out as <doc/>.
Serialization in general is tested within the XSLT tests.

    Eric> Finally, don't forget to update the file $GOBO/History.txt
    Eric> from time to time.

I will do that too when I have finished refactoring.
-- 
Colin Adams
Preston Lancashire

Re: [gobo-eiffel-develop] Please update History.txt

[Bernd S. <ber...@in...>]

On Sat, 06 Oct 2007 18:11:15 +0200, Eric Bezault <er...@go...>  
wrote:

> Hi Bernd,
>
> Would it be possible that you update the file $GOBO/History.txt to
> indicate what you have recently done in the Argument library?
> Thanks.
>

Done.
Bernd

[gobo-eiffel-develop] Serializer example

[Eric B. <er...@go...>]

Hi Colin,

Would it be possible that you add a Readme.txt file in your serializer
example explaining what it is and how to use it? All examples should
come with a Readme file.

Also, it would be nice if you could update the test class
$GOBO/test/example/xml/xm_etest_serializer.e to provide some input
sample and check the output, as it is done in other tests such as
the one for the schematron or for the argument library example.

Finally, don't forget to update the file $GOBO/History.txt from
time to time.

Thanks.

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

[gobo-eiffel-develop] Please update History.txt

[Eric B. <er...@go...>]

Hi Bernd,

Would it be possible that you update the file $GOBO/History.txt to
indicate what you have recently done in the Argument library?
Thanks.

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

Re: [gobo-eiffel-develop] Short options ambiguity in AP_OPTION

[Colin A. <col...@ho...>]

It works fine now.

Thanks.
_________________________________________________________________
100=92s of Music vouchers to be won with MSN Music
https://www.musicmashup.co.uk=

Re: [gobo-eiffel-develop] Short options ambiguity in AP_OPTION

[Bernd S. <ber...@in...>]

Colin Adams wrote:
> It should be there now.
>> I cannot find the serializer.e file. It looks like you forgot to check it 
> _________________________________________________________________
> The next generation of MSN Hotmail has arrived - Windows Live Hotmail
> http://www.newhotmail.co.uk

Committed fix, please try again.

Bernd

Re: [gobo-eiffel-develop] Short options ambiguity in AP_OPTION

[Colin A. <col...@ho...>]

It should be there now.
> I cannot find the serializer.e file. It looks like you forgot to check it=
=20
_________________________________________________________________
The next generation of MSN Hotmail has arrived - Windows Live Hotmail
http://www.newhotmail.co.uk=

Re: [gobo-eiffel-develop] Short options ambiguity in AP_OPTION

[Colin A. <col...@ho...>]

Well I didn't forget, but it hasn't been checked in all the same.=20
I will try again tonight.


> I cannot find the serializer.e file. It looks like you forgot to check it=
 =20
> in.


_________________________________________________________________
Get free emoticon packs and customisation from Windows Live.=20
http://www.pimpmylive.co.uk=