| There are still memory-leaks in Text_IO package (I think in the Low_Level_Text_IO).
I did regognize these errors with the Ultrix Dec Ada Compiler in 1993.
The answer from the DEC support was that You have other priorites than to correct this.
I heard that these errors are also implemented in the VMS Dec ADA Version.
We have systems working 24 hours 7 day a week. So this errors becomes a quality
factor of the software. Of course, we can program direct Unix access to the filesystem.
But we would like to program Ada code and not unportable direct Unix access code.
Try these two little programs and check your memory space.
DEC Unix V4.0b, DEC Ada V3.3
with Text_IO; use Text_IO;
procedure Name_Error_Test is
File : File_Type;
begin
loop
begin
open (File, IN_File, "Unknown_File");
-- the Unknown_File mustn't exist
exit;
exception
when Name_Error => delay 0.1;
end;
end loop;
end Name_Error_Test;
----------------------------------
with Text_IO; use Text_IO;
procedure IO_Leak_Test is
MY_File : File_Type;
begin
loop;
Create (MY_File, Out_File, "Text_IO_Leak.Dat",
"Owner => Read_Write_Execute, Group => Write, Other =>
Write");
Close (My_File);
delay 0.1;
end loop;
end IO_Leak_Test;
|
| Bucher & Suter AG wrote:
>
> At 07:57 20.03.97 +0000, you wrote:
> >Bucher & Suter AG wrote:
> >>
> >> At 13:58 19.03.97 +0000, you wrote:
> >> >Have you reported this problem to the Customer Support Centre? The
> >> >problem is being looked at by engineering now.
I need to know if this is the same problem that is being worked on by
Digital Customet Support in France.
> I tried to translate the low_level_io.ada in the library. Serveral packages
> becomes obsolet if I do that. I don't know the dependencies of the library
> packages. How do I translate the library?
I know very little about ada unfortunately, but I'm told that you can
compile it into a local library, for testing purposes at least.
|