Difference between revisions of "EiffelStudio Wish List"

Revision as of 10:40, 17 November 2006

Welcome to the Eiffel/EiffelStudio Wish List. This is the place where you, the community, get a chance to tell us what you think is important to include in the future versions of the Eiffel compiler and EiffelStudio IDE.

Please use this list responsibly and try to correctly categorize your wishes. A brief description may help us evaluate your requirements but please be brief.

Our stock pile of genie snared, dusty gold lamps is running low for our next release (EiffelStudio Releases) but we'll be sure to scour the lands for more.

Compiler

General

• A way to author Enum-like class for typed options or flags. Currently using INTEGER and a bag of analogous constants doesn't make Eiffel "elegant".

.NET

• Consume .NET generics. Not being able to use them is becoming harder.
  We cannot write Atlas (AJAX) based web applications because of it. The Visual Studio SDK, used by EiffelEnvision, is increasing it's use of generics and preventing use from supporting some features. The people who want to use the .NET framework classes instead of the Eiffel ones cannot use generics and have to resort to using the non-generic versions of list, which bulks implementation and leads ambiguity.
• Emit .NET generics types for Eiffel generic classes.
• Allow direct access to member of TYPED_POINTER [xxx] item out/ref routine arguments.
• Allow direct setting of TYPED_POINTER [xxx] item for out/ref routine arguments.
• Optimized call.do_nothing as a IL pop instruction to removed returned value.

IDE

• Give the user control over which classes will be compiled over the GUI (say: click on grey class and it becomes yellow and will be compiled always from now on, even though it may not be used at all. This is good for development of classes which are not added over GUI in ES.)

Other

• Provide a implementation for weak references.