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=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.107.30.16 with SMTP id e16mr3937090ioe.22.1518823329684; Fri, 16 Feb 2018 15:22:09 -0800 (PST) X-Received: by 10.157.64.65 with SMTP id o1mr283283oti.9.1518823329540; Fri, 16 Feb 2018 15:22:09 -0800 (PST) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!border1.nntp.ams1.giganews.com!border2.nntp.ams1.giganews.com!nntp.giganews.com!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!w142no574675ita.0!news-out.google.com!m16ni1897itm.0!nntp.google.com!w142no574673ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 16 Feb 2018 15:22:09 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=75.99.9.146; posting-account=s89PEgoAAABHs2ETFyOrCeTQVQJAfzKq NNTP-Posting-Host: 75.99.9.146 References: <789f6417-5e6f-4d5f-8abb-80246f4f405a@googlegroups.com> <5e5ce844-42a8-c2de-bf53-4acf67be7f53@bahnhof.se> <2bf467d9-dbc1-46e9-981f-a092f82e7271@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: GNAT user-specified (via Raise_Exception) warning message size limit From: marciant@earthlink.net Injection-Date: Fri, 16 Feb 2018 23:22:09 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Received-Body-CRC: 2625422419 X-Received-Bytes: 2702 Xref: reader02.eternal-september.org comp.lang.ada:50473 Date: 2018-02-16T15:22:09-08:00 List-Id: > I am curious to know the rationale for using pretty long exception messag= e. I have not had a situation to use exception message this long in my soft= ware career. Some XML text messages are being parsed "deep" down in a subsystem and when= a problem is encountered a specific exception is raised and the problemati= c XML text is included in the exception message and propagated up a "level"= or two of code where it is sometimes parsed again and repropagated with ad= ditional debugging information. I know: "That is abuse of exceptions!" :) = However, it seemed to be (and proved to be) an easy and robust way to debu= g and provide forensic logs of problems that occurred in the fielded system= s. The project had been frozen as ObjectAda 7.2.2 however we are investigating= the feasibility of moving to GNAT. The ObjectAda compiler either did not = have a size restriction or we luckily had not ever reached it! Anyway, thi= s seems to be the last sticking point before a simple proof-of-possibility = can be demonstrated. (I might first have to try to design some addition me= chanism that can be utilized very much "under the covers" that allows the c= urrent architecture to remain mostly intact.)