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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a24:bdc7:: with SMTP id x190-v6mr9382610ite.29.1538765012128; Fri, 05 Oct 2018 11:43:32 -0700 (PDT) X-Received: by 2002:aca:3094:: with SMTP id w142-v6mr218189oiw.0.1538765011801; Fri, 05 Oct 2018 11:43:31 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.166.215.MISMATCH!z5-v6no98734ite.0!news-out.google.com!l70-v6ni83itb.0!nntp.google.com!x98-v6no99785ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 5 Oct 2018 11:43:31 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=2001:14bb:51:2563:5c83:217e:4aa9:f00; posting-account=9KbC2woAAAA0kK2IAUr3-FkzJBtOzrhm NNTP-Posting-Host: 2001:14bb:51:2563:5c83:217e:4aa9:f00 References: <0f5608ef-0038-491c-b15f-f67bcc76fae8@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <47d1c0fd-bfb6-4215-8cf5-c3ce66c882b6@googlegroups.com> Subject: Re: Record operations (Algebraic Data Types and printing) From: =?UTF-8?B?SGVucmlrIEjDpHJrw7ZuZW4=?= Injection-Date: Fri, 05 Oct 2018 18:43:32 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader02.eternal-september.org comp.lang.ada:54491 Date: 2018-10-05T11:43:31-07:00 List-Id: On Friday, 5 October 2018 21:32:59 UTC+3, Niklas Holsti wrote: > Nope, and too bad. That's something that would often be useful at the=20 > program development stage. But not so useful when the program is in=20 > production runs, for typical Ada applications. >=20 > One way to get something like this is to run the program under a=20 > debugger, and ask the debugger to display the record variable. Debuggers= =20 > can usually show "component-name =3D value" pairs. Yes, actually my second option was to look at the real debugger. It seems t= hat GPS is nicely equipped with gdb interface and after adding the debug an= d symbol flags to the compilation, I can step on the debugger and hover wit= h mouse cursor on the record instance to see the components and values. Ver= y nice! > I seem to remember seeing a posting here, a few years ago, offering a=20 > tool that would construct an Image function for a given record type. The= =20 > tool was possibly based on ASIS, and possibly not. Sadly I did not find= =20 > any links to this, but perhaps someone else has a better memory or=20 > better search methods. That would be cool, but honestly, after using the debugger, the prints are = just too much to bother with. :) Perhaps in plain text console environment = that would play it's part, but now I think I'll just go with the debugger. -Henrik