-- During exception handling, use function -- Ada.Exceptions.Exception_Information(EO) instead of Ada.Exception_Name (EO) -- & Ada.Exception_Message (EO). Of course, EO stands for Exception_Occurrence -- type. The advantage of this usage is that Exception_Information has all -- capabilities of Exception_Name and Exception_Message combined. In addition, -- function Exception_Information also gives full call stack trace back for -- most platforms. -- -- Anh Vo
I agree with the above at least for the GNAT compiler. I remember advocating this view, but then someone (could it have been Tero Koskinen who has experience with several different Ada compilers?) informed me that the Ada standard has more restrictions on what Ada.Exception_Name (EO) and Ada.Exception_Message (EO) contains and that there is less restriction on what Exception_Information should contain. The argumentation was that if one wants to be cross-compiler one should stick to Exception_Name and Exception_Message for the application to exhibit similar exception error messages. My experience is that Exception_Information with the GNAT compiler works as described above and works very well. While we are on the subject on exceptions. There is no way to get stack trace information if one uses GNAT GPL 2015, right? I mean, there is no addr2line. By the way, in an earlier post I wrote about some issue in the HTTP Client implementation in simple compnonents. I can report that it works very well. Best regards, Joakim Strandberg
------------------------------------------------------------------------------
_______________________________________________ Gnoga-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gnoga-list
