Re: ADA Popularity Discussion Request

[jayessay <nospam@foo.com>]

chad.rmeiners@gmail.com (Chad R. Meiners) writes:

> "jayessay" <nospam@foo.com> wrote in message 
> news:m3acw0bl1u.fsf@rigel.goldenthreadtech.com...
> > with Text_Io; use Text_Io;
> >
> > procedure Foo is
> >
> >   type Hex_Num is mod 16;
> >
> >   function Hext (N : Integer) return Hex_Num is
> >   begin
> >      -- == (1+ (n mod 16)), which is the logic error.
> >      return Hex_Num(1 + (N mod Hex_Num'Modulus));
> >   end Hext;
> 
> However, most Ada programmers would have written it like
> 
> procedure Foo is
>     type Hex_Num is mod 16;
> 
>     function To_Hex_Num(Item : Integer) return Hex_Num is
>     begin  -- This function provides the correct conversion
>            -- for use by all other subroutines.
>         return Hex_Num(Item mod Hex_Num'Modulus);
>     end To_Hex_Num;
> 
>     function Hext (N : Integer) return Hex_Num is
>     begin
>         return 1 + To_Hex_Num(N);  -- Note To_Hex_Num(1+N) also works
>     end Hext;
> 
>     ...
> 
> and avoided the problem altogether.

All you are saying is that _the programmer_ would have caught the
logic error!  In this ridiculously simple case, sure.  The Lisp
programmer would never have brain farted like this in this simple case
either!!  The point is, the programmer in this case, Georg Bauhaus,
_did_ make the error and did not avoid the problem!


/Jon

-- 
'j' - a n t h o n y at romeo/charley/november com