home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!usenet.ins.cwru.edu!news.ysu.edu!malgudi.oar.net!zaphod.mps.ohio-state.edu!moe.ksu.ksu.edu!mccall!mccall!tp
- Newsgroups: vmsnet.misc
- Subject: Re: Output conversion warnings in Vax Fortran
- Message-ID: <1992Oct12.122509@mccall.com>
- From: tp@mccall.com (Terry Poot)
- Date: Mon, 12 Oct 1992 12:25:09 CST
- Reply-To: tp@mccall.com (Terry Poot)
- References: <1992Oct12.112837.18130@monu6.cc.monash.edu.au>
- Organization: The McCall Pattern Co., Manhattan, KS, USA
- Nntp-Posting-Host: mis1
- Nntp-Posting-User: tp
- Lines: 23
-
-
- In article <1992Oct12.112837.18130@monu6.cc.monash.edu.au>,
- bena@yoyo.cc.monash.edu.au (Ben Aveling) writes:
- >I'm sure anyone who has ever used Fortran has seen the ***** type output
- >when a number is too big to fit in it's format statement. My gripe is
- >that every time my programs do that, it counts as a warning, and does a
- >stack dump. Can some kind soul please tell me how I can stop this
- >happening, short of turning off all messages.
-
- This probably isn't the answer you wanted, since it involves editting your
- source (presumably a lot of it) but if there is an iostat=<xx> specifier in your
- I/O statement, the stack dump won't appear.
-
- I suppose the correct solution that doesn't involve changing your I/O statements
- would be to provide a condition handler that checked for that specific condition
- and resignalled all others. I'd imagine you could put such a condition handler
- on your main program. I expect it is the default condition handler that produces
- the stack dump. If it's one down in the FORTRAN RTL, then this won't work, and
- you'll have to use IOSTAT.
- --
- Terry Poot <tp@mccall.com> The McCall Pattern Company
- (uucp: ...!rutgers!depot!mccall!tp) 615 McCall Road
- (800)255-2762, in KS (913)776-4041 Manhattan, KS 66502, USA
-