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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,5edee74b13d8e50a X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!news.glorb.com!feeder.erje.net!news2.arglkargh.de!news.n-ix.net!news.belwue.de!LF.net!news.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: The "black magic" of ioctl Date: Sun, 24 Oct 2010 19:58:04 +0200 Message-ID: <87bp6j4gnn.fsf@mid.deneb.enyo.de> References: <74b46743-fb81-48cc-a478-ffd069db2fc6@k22g2000yqh.googlegroups.com> <877hh8lkok.fsf@mid.deneb.enyo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: idssi.enyo.de 1287943084 5247 172.17.135.6 (24 Oct 2010 17:58:04 GMT) X-Complaints-To: news@enyo.de Cancel-Lock: sha1:irfZhZDcLov8vgUegSEwpd9bfmQ= Xref: g2news1.google.com comp.lang.ada:14720 Date: 2010-10-24T19:58:04+02:00 List-Id: * Simon Wright: > Florian Weimer writes: > >> In addition, the ioctl constants are often difficult to extract from >> the header files. The best way to get them seems to be a small C >> program which just prints them. > > It could print them as an Ada spec; no manual handling required! Sure (and I did that in similar cases). By the way, is there a good way to integrate such source code generation into the gnatmake project-based build system?