Difference between revisions of "Wish list"

From Liberty Eiffel Wiki
Jump to navigation Jump to search
 
(attributes are ok to me)
(One intermediate revision by the same user not shown)
Line 69: Line 69:
 
no new functionality at all, but for documentations it would be very nice :-).
 
no new functionality at all, but for documentations it would be very nice :-).
 
--Interested SmartEiffel user
 
--Interested SmartEiffel user
  +
  +
My opinion is that the "attribute" idea is a good idea. If other members of the team
  +
are ok too, this will be added one day in the SmartEiffel language.
  +
--[[User:Colnet|Colnet]] 12:12, 10 Nov 2005 (CET)
  +
  +
I don't mind. Indeed it's a nice documenting tool. Especially for contracts. --[[User:Cadrian|Cyril]] 08:50, 12 Nov 2005 (CET)

Revision as of 08:50, 12 November 2005

If you have a request to improve SmartEiffel, to improve the SmartEiffelWiki, to ask for a new page in the Grand SmartEiffel Book or, to propose a modification of the Eiffel language of SmartEiffel, please, update this page yourself. Do not forget to sign thanks to the ~~~~ special command which gives:
Colnet 19:19, 21 Jun 2005 (MET DST).

Exception handling

My highest priority request is to improve exception handling. If an exception is caught by a "rescue" clause but remains active because there is no "retry", then the stack dump should still be printed on program termination. --Roger Browne 12:54, 13 Jul 2005 (CEST)

Yes. I don't know how the runtime behaves in that case. Meanwhile, I think a workaround is to call ANY.print_run_time_stack in your rescue clause. --Cyril 15:00, 13 Jul 2005 (CEST)

Unfortunately this doesn't work, as has been discussed many many times. It only prints the unwound stack. --Roger Browne 17:33, 18 Jul 2005 (CEST)

Well, forgive my poor forgetting mind... I thought all was solved in this area now since sz:469 is fixed. --Cyril 10:10, 28 Jul 2005 (CEST)

COMMAND_LINE_TOOLS

I would very much like some documentation and/or tutorial example on how to write a new EXTERNAL_TOOL using COMMAND_LINE_TOOLS. The underlying acyclic visitor pattern has been explainhed a couple of times on the ML and I am also aware of http://smartzilla.loria.fr/attachment.cgi?id=180&action=view but what I miss is some more basic information, e.g. what exactly does the tree of visitable objects look like and how does it relate to the system being parsed? With such documentation, people would be able to write plugins for non-Eiffel specic IDEs, class browserts and the like. --Frank

The best (most up-to-date) tutorial currently available is eiffeldoc, which is an EXTERNAL_TOOL and extensively uses Visitors. Of course more information will be added in this wiki. It will be available there. --Cyril 00:25, 18 Jul 2005 (CEST)

German translator wanted

I am looking for german native speakers ready to follow the translation in german of the Grand Book. --Colnet 17:33, 15 Jul 2005 (CEST)

It would be great to also have a Spanish translation. And all the other languages are welcome too. --Cyril 00:25, 18 Jul 2005 (CEST)

Spanish translator wanted

I'm not a person with a lot of extra time, but could work in the spanish translation. What must be done to start a new language section? --Dmoisset 01:07, 30 Jul 2005 (CEST)

Same thing for me & German: Have little time, but could help.--Coertel 08:21, 2 Aug 2005 (CEST)

The Spanish and German languages have been created. Fell free to start feeding them. --Cyril 09:45, 6 Aug 2005 (CEST)

Class TREE

I would like to have a Class TREE be added to the library. --User:Colonna 12:53, 24 Sep 2005 (CEST)

Incremental Eiffel compilation

Incremental compilation of the Eiffel sources, not only of the generated C code. --Anonymous

What for? Do you mind the compiler is too slow? --Colnet 03:13, 21 Oct 2005 (CEST)

New keyword "attribute"?

What's your opinion about the integration of "attribute" into SmartEiffel? Of course there would be no new functionality at all, but for documentations it would be very nice :-). --Interested SmartEiffel user

My opinion is that the "attribute" idea is a good idea. If other members of the team are ok too, this will be added one day in the SmartEiffel language. --Colnet 12:12, 10 Nov 2005 (CET)

I don't mind. Indeed it's a nice documenting tool. Especially for contracts. --Cyril 08:50, 12 Nov 2005 (CET)