Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!uupsi!ccavax!merriman From: merriman@ccavax.camb.com Newsgroups: comp.lang.c Subject: Re: signals, longjmp, and ANSI C Message-ID: <24654.265c32f6@ccavax.camb.com> Date: 24 May 90 23:16:06 GMT References: <1990May17.191259.28271@athena.mit.edu> <12890@smoke.BRL.MIL> <1990May18.225103.11948@ux1.cso.uiuc.edu> <+3L3+E@xds13.ferranti.com> <328:May2219:52:1390@stealth.acf.nyu.edu> <24581.265ae798@ccavax.camb.com> Lines: 30 Distribution: usa Organization: Cambridge Computer Associates, Inc. Lines: 26 In article , peter@ficc.ferranti.com (Peter da Silva) writes: > I said: you can't do system calls inside RSX ASTs. > > In article <24581.265ae798@ccavax.camb.com> merriman@ccavax.camb.com writes: >> Really? I've never heard of a restriction against making system calls from >> an asynchronous trap in RSX. I've done it many times with no trouble -- >> I learned the technique from a DEC RSX programming class. > > It's been too long, so I may have misremembered. This was in 11/M, not M+. > There were restrictions as to what you could do in an AST, but I guess it's > not as extreme as that. You can do anything in a VMS or RSX AST that takes into consideration the logical concurrency issues involved in the application. Most native library and system services are designed to be AST-re-entrant. Some brain-dead C RTL implementations don't understand what this means. > > Anyway, you sure couldn't longjmp out of one, at least not in 11/M. I know > that because I wanted to do it for a Forth implementation. longjump is not an RSX concept. You must have been using something cobbled up to mimic UNIX behavior rather than taking advantage of the operating system features. > -- > `-_-' Peter da Silva. +1 713 274 5180. > 'U` Have you hugged your wolf today? > @FIN Dirty words: Zhghnyyl erphefvir vayvar shapgvbaf.