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=-0.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, HK_RANDOM_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f849b,869d7890f1bd9878,start X-Google-Attributes: gidf849b,public X-Google-Thread: 103376,869d7890f1bd9878,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-02-17 16:06:57 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: berndtrog@yahoo.com (Bernd Trog) Newsgroups: comp.lang.ada,comp.arch.embedded Subject: Type-safe low-level programming? Date: 17 Feb 2003 16:06:56 -0800 Organization: http://groups.google.com/ Message-ID: NNTP-Posting-Host: 212.185.252.194 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1045526816 22332 127.0.0.1 (18 Feb 2003 00:06:56 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 18 Feb 2003 00:06:56 GMT Xref: archiver1.google.com comp.lang.ada:34182 comp.arch.embedded:59675 Date: 2003-02-18T00:06:56+00:00 List-Id: Hi, lets say I've something like this: pragma No_Run_Time; type Bit_Number is range 0 .. 7; type Address_Type is range 0 .. 16#ff#; Register_A : constant Address_Type := 1; Bit_A1 : constant Bit_Number := 4; --Register A, Bit 4 Bit_A2 : constant Bit_Number := 1; Bit_A3 : constant Bit_Number := 7; Register_B : constant Address_Type = 2; Bit_B1 : constant Bit_Number :=4; Bit_B2 : constant Bit_Number :=2; Bit_B3 : constant Bit_Number :=5; [...] Register_Z : constant Address_Type = 2; Bit_Z1 : constant Bit_Number :=6; Bit_Z2 : constant Bit_Number :=0; Bit_Z3 : constant Bit_Number :=5; procedure Set_Bit( Adr : in Address_Type; Nr : in Bit_Number ); procedure Clear_Bit( Adr : in Address_Type; Nr : in Bit_Number ); On a not-so-good day I wrote: Set_Bit( Register_A, Bit_B3 ); and found my error days later :-( Now I wonder, if its possible to make 'Set_Bit' type-safe *without* increasing the program memory size for every new register? Bernd