From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1592759aa83d0d45 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-02 08:55:05 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!skynet.be!skynet.be!freenix!enst.fr!not-for-mail From: Lionel.DRAGHI@fr.thalesgroup.com Newsgroups: comp.lang.ada Subject: RE: Suggestion for Ada 200x - Interface inheritance Date: Mon, 2 Jun 2003 17:57:22 +0200 Organization: ENST, France Message-ID: NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: avanie.enst.fr 1054569301 1688 137.194.161.2 (2 Jun 2003 15:55:01 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Mon, 2 Jun 2003 15:55:01 +0000 (UTC) To: comp.lang.ada@ada.eu.org Return-Path: X-Mailer: Internet Mail Service (5.5.2653.19) X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: comp.lang.ada mail to news gateway List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:38373 Date: 2003-06-02T17:57:22+02:00 | -----Message d'origine----- | De: Steve [mailto:nospam_steved94@attbi.com] ... | What do you think of the idea of also optionally giving the | mode of the | parameter, which if present must match the function or procedure | declaration. That is, extending the above example: | | result := Add( in left => 2, in right => 3 ); | | Why? Readability. When reading code it is sometimes unclear from the | caller whether or not a procedure modifies its parameters. Yes, and i often need to "navigate" up to the operation declaration to see parameter's mode. My idea was to introduce "<=" for out parameters and "<=>" for in out. Example: Create (File <=> My_File, Mode => In_File, Name => "My_File", Status <= Status); Pretty clear, isn't it? :-) And could also apply to declaration! Anyway, some ada-mode colouring parameters according to their mode would do the job just fine for me. -- Lionel Draghi