mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-07 15:22:31 +01:00
Author:tedf
Date:2011-05-12T01:58:13.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@891 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -1,15 +1,23 @@
|
||||
[[Property:title|Major changes between ISE Eiffel 6.7 and ISE Eiffel 6.8]]
|
||||
[[Property:link_title|6.8]]
|
||||
[[Property:weight|-15]]
|
||||
[[Property:uuid|9d06aeec-a75e-3b39-b19a-c6b19fe9f6b8]]
|
||||
[[Property:uuid|4ae502ce-5832-c323-4c3a-d1b0d1243735]]
|
||||
==What's new==
|
||||
{{seealso|[[Differences between standard ECMA-367 and Eiffel Software implementation|Differences between standard ECMA-367 and Eiffel Software implementation]] }}
|
||||
|
||||
==Improvements==
|
||||
* Improved keyboard navigation in the Info tool.
|
||||
* Extended types supported by EiffelStore, especially STRING_32 for Unicode string types.
|
||||
* Improved memory management in EiffelStore, ODBC implementation.
|
||||
* Set file name of current class to the Save File As dialog.
|
||||
|
||||
==Changes==
|
||||
|
||||
==Bug fixes==
|
||||
* Various bug fixies in EiffelStore.
|
||||
* Fixed the bug in the Info tool when deleting an EIS entry, selecting No did not actually cancel the deletion.
|
||||
* Fixed bug#17374: Feature call on void target in {EB_CLASS_INFO_ANALYZER}.stone_in_click_ast in EiffelStudio
|
||||
* Fixed bug#17299: Locale preference lost the second time opening ES.
|
||||
|
||||
===Language issues===
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ The pre-parse processing gives the <code>EIFFEL_PARSER_POOL</code> an agent that
|
||||
|
||||
When an <code>EIFFEL_PARSER</code> finishes with a file, it calls the agent for post-parse processing. In this way, it notifies the instance of <code>DEGREE_5</code> that it is done with that file.
|
||||
|
||||
So, it is here that elements of the observer pattern are shown. In more typical observer pattern examples, there is one observed object an a set of one or more observers. But here, there is one observer, the instance of <code>DEGREE_5</code>, and many observable objects, the parsers. Also, instead of making calls directly to the observer, the observed objects apply the agents that have been provided by the observer.
|
||||
So, it is here that elements of the observer pattern are evident, just in a slightly non-typical way. In more typical observer pattern examples, there is one observed object and a set of one or more observers. But here, there is one observer, the instance of <code>DEGREE_5</code>, and many observable objects, the parsers. Also, instead of making calls directly to the observer, the observed objects apply the agents that have been provided by the observer.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user