Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!munnari.oz.au!bruce!trlluna!trlamct!greg From: greg@trlamct.trl.oz.au (Greg Aumann) Newsgroups: comp.lang.eiffel Subject: Re: Good problems (and Eiffel 2.3) Message-ID: <2070@trlluna.trl.oz> Date: 13 Aug 90 01:52:59 GMT References: <104@alfrat.uucp> Sender: root@trlluna.trl.oz Lines: 67 From article <104@alfrat.uucp>, by roy@alfrat.uucp (Roy Phillips): > With reference to your problem #5: GOOD segmentation violation > > This problem is not an unknown phenomenon to me, below is a list of > three things worth checking: > I have run accross this problem also. There is a problem when using GOOD with SUN's OpenLook server, at least with the 1.02beta version. It did however work with MIT's release 4 server. The same bug is demonstrated in the menu example program. See the execution trace below. I have reported this to ISE. I would like to see ISE publish a known bugs or problems list with patches or work arounds. This I am sure would save many people a lot of time. Also every now and again someone from ISE posts a patch. It would be very useful if this process was a little more formalised as it is in the source groups. By this I mean using context diffs so they can be safely applied automatically using patch(1) and including some sort of numbering or dating scheme eg patchlevels or the patch dates al la Cnews. --- tardis% demo Event type = 11 Internal error in function fill_input System execution failed. Below is the sequence of recorded exceptions: -------------------------------------------------------------------------------- Object Class Routine Nature of exception Effect -------------------------------------------------------------------------------- 1E465C GRAPH_SHELL execute Feature "handle": Applied to void reference. Fail -------------------------------------------------------------------------------- 1E465C GRAPH_SHELL execute Routine failure. Fail -------------------------------------------------------------------------------- 1E5E0C DEMO create Routine failure. Fail -------------------------------------------------------------------------------- tardis% --- To Christiane Greitmann - I have sent you some email but I am not all that confident that it will arrive. Please let me know if you don't get it. > The first thing to try is to create a trivial class containing, for example, > just an INTEGER feature, create the .eiffel with the smallest UNIVERSE, and > run good - this should always work. > > Lastly, do you have 2.3 yet? the graphics library is far superior, in my view, > than the previous version - you might not have to mess around with the C > interface (urrgh!) at all, unless you're into serious 3D animation applications. Does this mean that Eiffel 2.3 is released? If so when will those with support contracts get it? Perhaps someone from ISE could post the release notes. You say the graphics classes are usable does this mean that they now have a proper interface to X Windows and not this attempt at a generic windows interface complete with floating point co-ordinates? I consider that the lack of a good X windows user interface toolkit is, for me at least, one of the most serious deficiences of Eiffel and would be enough reason for me to use C++ on my next project despite the fact that I think Eiffel is a superior language. Greg Aumann ------------------------------------------------------------------------- Artificial Intelligence Systems Email: g.aumann@trl.oz.au Telecom Research Laboratories Voice: +61 3 541 6222 Melbourne, AUSTRALIA Fax: +61 3 543 8863