Remove features entry and enter

Proposal

Proposal for class ARRAY:

Remove features 'entry' and 'enter'.

Please select one of the following:

Strongly accept the proposal
Accept the proposal
Reject the proposal
Strongly reject the proposal
Don't mind (happy either way)
Abstain (not happy either way)

History

These features were introduced in the 1995 standard, and are supported by ISE, HACT and VE but not SE.

Background

enter is a non-frozen synonym of put, and entry is a non-frozen synonym of item.

Rationale

If put and item are not frozen, then enter and entry are not needed because put and item can be redefined.

If put and item are frozen, then we cannot safely redefine enter and entry in a descendant, because put and item will then have erroneous behaviour.

Discussion

I can't find any discussion of this issue.

Impact of proposed change

Low.

A vendor may retain entry and enter in their implementation, even if they are dropped from the standard. Alternatively, a vendor may declare entry and enter "obsolete" and recommend to use put and item instead.

Result

This proposal was accepted into the ELKS2000 draft on 20 October 1999.

Voting details

votes cast at eGroups:

Accept the proposal
                sergei_ivanov@object-tools.com
                steinman@sco.edu
                joachim.durchholz@halstenbach.de
                kevin@ethossoft.co.nz
                jcm@mstr.hgc.edu
                ericb@gobosoft.com
                jweirich@one.net
                sparker@eiffel.ie
Strongly accept the proposal
                chcouder@club-internet.fr
                manus@eiffel.com
                richieb@netlabs.net
                genepi@sympatico.ca
                simonwillcocks@enterprise.net
                tking@insystems.com
                franck.arnaud@omgroup.com
                kwaxer@aha.ru
Reject the proposal
                ansible@xnet.com

votes sent to the discussion list: