converting my employer to Ada?

[lmiller@indyvax.iupui.edu]

Hello,

I just recently switched jobs, from a position where I used Ada to one where
the language of choice is C/C++.  We will be using LYNX as our host OS and will
be developing multithresded applications for real time systems.  I've been
boning up on the ins and outs of posix threads in the LYNX manuals and was
looking at the examples.  I was struch by the ammount of error checking code
required in C (especially if you check the return value from everything you
call).  I also thought that compared to Ada tasking, POSIX threads are an
outrageous pain in the ass by comparison.  Being the Ada genious that I am, I
thought to myself "Why don't they just switch to Ada and be done with all this
extra error checking ^h^h^h^h^h^h^h^h^h^h^h result checking and POSIX thread
hoop jumping.  

How would the Ada mavens out there in net land suggest I bring my idea to my
new (just 4 days so far) employer, with the associated supporting documentation
to prove my case?  They will not be porting a considerable ammount of code from
old systems to the new system, so that's not an issue.  They are a small outfit
and from what I've heard, been scared from what the've heard about Ada.  BTW I
did use Ada two employers back to do the exact same kind of work.  

-- Dana (Who still shudders at the sight of 
         if ((result_value = uglyPosixCall(foo)) != TRUE) {
           _goUddersUp((void) bar);
         }
         )