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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,e51f94f876618e37 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII Received: by 10.224.186.20 with SMTP id cq20mr6671841qab.8.1352498657899; Fri, 09 Nov 2012 14:04:17 -0800 (PST) Received: by 10.236.88.236 with SMTP id a72mr1923817yhf.20.1352498657879; Fri, 09 Nov 2012 14:04:17 -0800 (PST) Path: gf5ni18188417qab.0!nntp.google.com!c7no14871812qap.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 9 Nov 2012 14:04:17 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=206.53.78.59; posting-account=ShYTIAoAAABytvcS76ZrG9GdaV-nXYKy NNTP-Posting-Host: 206.53.78.59 References: <9bbd99bd-f953-434d-b3c8-6e8a6d5c7dfd@googlegroups.com> <77906f56-8ea0-4d87-8ace-4db1172958cd@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <6b1d2c76-baf9-4c9b-b6c7-51c92f3cb561@googlegroups.com> Subject: Re: Question[s] about aliased extended return. From: sbelmont700@gmail.com Injection-Date: Fri, 09 Nov 2012 22:04:17 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-11-09T14:04:17-08:00 List-Id: On Friday, November 9, 2012 4:44:19 PM UTC-5, Hibou57 (Yannick Duch=EAne) w= rote: >=20 > Just out of curiosity, for a thin binding, would reuse the names used in = =20 >=20 > the API or would you change names only in a tick binding? (most of times,= =20 >=20 > I feel API names are not nice to read). >=20 My preference for the thin binding is to reuse the name exactly as it in th= e C API, import the actual C function with a preceeding 'C_', and then clea= n up the thick binding as needed (usually it ends up being split apart into= child packages, depending on the API), but of course to each their own. -sb