"J-P. Rosen" wrote in message news:p7898p$1arv$1@gioia.aioe.org... > Le 01/03/2018 à 00:23, Randy Brukardt a écrit : >> "Mehdi Saada" <00120260a@gmail.com> wrote in message >> news:15c49c4e-726a-4fd7-bf35-c7d27ff9a491@googlegroups.com... >>> Thanks. >>> But that's ugly... How about fixing this for the next norm ? >> >> Does anyone other than ACATS tests actually use stubs these days? Why? >> (We >> used to use them extensively, but only because Janus/Ada on 16-bit MS-DOS >> limited a single unit to 64K of generated code -- and our editors >> couldn't >> handle more than 256K of source code at a time. None of that makes sense >> today.) > At least for task and protected bodies, which can't be child units. > > Also, stubs have visibility to elements in the parent's body, although I > agree that direct visibility of global elements should be limited. Yes, but why put them in a separate file in the first place? The only reason I know not to do that is that editors (and compilers) used to have size limits. It's usually easier to have one big file because it makes fewer places to look for things. (The subunits in Janus/Ada are annoying because one opens the body to find something only to find it isn't there and a different file has to be opened. Often, I don't know exactly what I'm looking for and have to bounce back and forth several times.) Randy.