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,4f9a2b7c164500f2 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.181.13.205 with SMTP id fa13mr823275wid.3.1354476177839; Sun, 02 Dec 2012 11:22:57 -0800 (PST) Received: by 10.49.63.164 with SMTP id h4mr1684181qes.39.1354476177503; Sun, 02 Dec 2012 11:22:57 -0800 (PST) Path: ha8ni98571wib.1!nntp.google.com!m1no16628230wiv.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 2 Dec 2012 11:22:57 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.153.71.190; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 69.153.71.190 References: <8ecc163c-7772-4528-a0d0-eb1ecfd67d98@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <975373f9-2184-4054-8b67-4f232f589bca@googlegroups.com> Subject: Re: Ada on Raspberry Pi: new article in MagPi issue 8 From: Shark8 Injection-Date: Sun, 02 Dec 2012 19:22:57 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-12-02T11:22:57-08:00 List-Id: On Sunday, December 2, 2012 9:19:56 AM UTC-8, Luke A. Guest wrote: >=20 > I'm also trying to think of a good project to document in the next articl= es, I > have two ideas, but not sure about them. The aim would be to show the use= of: >=20 >=20 > 1) packages Excellent idea, packages are really a fundamental Ada building-block and sh= ould be introduced early-on. > 2) possibly separates for platform dependencies Good idea, but you may want to deffer that to a bit later... perhaps after = introducing #4 and representation clauses -- if you go with using represent= ation clauses for low-level interfacing you can introduce separates for HW = variations.=20 > 3) GNAT project files & Makefiles GPR files do seem to be _much_ better than makefiles; however, it is platfo= rm [toolchain, rather] specific.=20 > 4) Representation clauses for mapping to hardware or C API's Reading your articles I would suggest you do the main article on hardware-m= apping and sidenote C-API interfacing and perhaps a small example w/layouts= .=20 > 5) Maybe tasking Tasking is one of Ada's excellent features, IMO. If we are going to introduce kids to programming via Ada, it might well beh= oove us to spoil them on parallel-computing w/ tasks. >=20 > Any ideas? It has to have a cool factor. Mine are: >=20 > 2) A language compiler going from source -> ELF/ARM binary. Might I suggest an interpreter? You could explain it a bit more succinctly = [and with less jargon (no need to go into linking, object files, loaders, e= tc)] than a compiler. (To keep syntax & parsing simple you could go with th= e old-school/early-computing LISP.)