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: 103376,8e11100f675ea2df X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII X-Received: by 10.66.72.232 with SMTP id g8mr6423625pav.23.1357241764949; Thu, 03 Jan 2013 11:36:04 -0800 (PST) Path: s9ni80117pbb.0!nntp.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.earthlink.com!news.earthlink.com.POSTED!not-for-mail NNTP-Posting-Date: Thu, 03 Jan 2013 13:36:04 -0600 Date: Thu, 03 Jan 2013 11:29:58 -0800 From: Charles Hixson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: asynchronous task communication References: <1c2dnd5E6PMDR33NnZ2dnUVZ_sednZ2d@earthlink.com> <50e18094$0$6583$9b4e6d93@newsspool3.arcor-online.net> <7NednS4s2oukfXzNnZ2dnUVZ_oadnZ2d@earthlink.com> <7cudnYloBfQDw3_NnZ2dnUVZ_rKdnZ2d@earthlink.com> <6bqdndEYjoxeGHnNnZ2dnUVZ_sadnZ2d@earthlink.com> In-Reply-To: Message-ID: X-Usenet-Provider: http://www.giganews.com NNTP-Posting-Host: 216.244.16.210 X-Trace: sv3-y1xc4pCgcGwfpZSB0wkQFAbDQ06TCuAhZXglfGWSmBFuncwirw6GDhHxWk4WOxOvj0pTmXQSc+OausU!OPvmWZKYqqPGd1l8IjlcIF9qjedkMJHCiPWcPDmpF/OBQ9prm58t8YHXzSa/W32OKh9mj9Oibvfb!7BgYGmwXp5RB6fqYNe2XBA== X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 4230 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Date: 2013-01-03T11:29:58-08:00 List-Id: On 01/03/2013 02:01 AM, J-P. Rosen wrote: > Le 03/01/2013 01:20, Charles Hixson a �crit : >> Adabrowse can be used to produce decent end-user documentation, but I >> want developer documentation. That means documenting >> function/procedures/types/etc that only exist in *.adb files. > Just put comments after the specification. These will show up when you > fly over any occurrence of the subprogram name in GPS - Very convenient I've just given up on using GPS. Perhaps it works better on MSWindows, but there are too many "silent failures". Last time it wouldn't generate a docs file because I'd forgotten a "private" declaration, but it didn't even tell me that it failed. Building the program fails, but not silently. I also don't like the way it handles tabs. (My default tab is 3 spaces, not 8, but if there's a way to customize this, I haven't found it.) Etc. Many other small annoyances. I prefer a simple editor with a command pane, like geany or kate. At least when things fail, they let you know why. However currently I'm using Eclipse, because the "simple editors" don't recognize Ada symbols. But the Eclipse plug-in seems to be highly version specific, so I may fall back to the editors yet. (The editors *do* have Ada specific highlighting, though.) > >> I'm after >> something that makes it easy for me to see what routines I've written, >> what they're called, what they're for, > The outline view in GPS shows you this - and the flyover feature of GPS > works there too > >> and any notes to myself that >> aren't appropriate for compile time warnings. I want to be able to come >> back to the code in 6 months or a year and figure out what it's doing >> easily. > Especially for implementation, nothing beats appropriate (repeat: > "appropriate") comments in the code. Yes. What I've found, that looks as if it will do what I want, is called NaturalDocs. It's not very Ada-specific, so it could be a lot better, but it recognizes Ada comments, and it has a useful selection of keywords. (It would be nice if it distinguished between function and procedure is the main problem I've noticed so far, but it's clear that there will be others, as Ada programs aren't structured the same way that programs in C, C++, or Java are structured. And I wish the output form were more compact. People spend too much time (or possibly not, as it may be easy) making the format glitzy at the cost of compact readability.