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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,680f4c169f5fad47 X-Google-Attributes: gid103376,public From: Scott Ingram Subject: Re: Raising IO_EXCEPTIONS.END_ERROR in a loop Date: 1997/11/19 Message-ID: <34731EB4.19661F3C@silver.jhuapl.edu>#1/1 X-Deja-AN: 290769126 References: <3472EEAE.65B43D71@silver.jhuapl.edu> <347302AE.7DFF@gsfc.nasa.gov> Organization: Johns Hopkins University Applied Physics Laboratory Newsgroups: comp.lang.ada Date: 1997-11-19T00:00:00+00:00 List-Id: Stephen Leake wrote: > > Scott Ingram wrote: > > > > The following fragment compiles, and even runs correctly through > > one iteration but blows up when re-reading a string from standard (extra lines snipped) > > You need to be more precise about what happens - "blows up" is not > something my computer does very often :). Does it raise an exception? > crash your OS? Are you running on Windows or some other OS? You are > using Get_Immediate, which is (unfortunately), system-dependent. What > compiler are you using? > Sorry, thought that "Raising IO_EXCEPTIONS.END_ERROR ..." as a subject line was specific enough to elucidate how it was blowing up :-) Also, I realize that Get_Immediate is system dependent: but I didn't realize HOW dependent, since I have only been using in a loop as illustrated when I wanted to hand feed some value in. Up until now, it appeared to behave the same way (for my purposes) on several varieties of Unix (including Linux.) > Jumping way out on a limb, I assume you have the same system I do > (Windows 95, GNAT 3.09) (yes, I'll upgrade to GNAT 3.10 one of these > days; I was holding out for an ada-aware debugger :( ). I compiled and > ran your code, after adding the missing declarations. It works fine, > except on this system Get_Immediate doesn't return until the user hits > , so you need to add Skip_Line. > > Hope this helps. (more stuff snipped) Yes, it does. I didn't think to try it on a sufficiently different system than the two where the problem showed up! Thanks. > -- > - Stephe -- Scott Ingram Sonar Processing and Analysis Laboratory Johns Hopkins University Applied Physics Laboratory