Re: To 'Call' or not to 'Call'
Access is OK even though it has automatic type up-conversion within a statement. The one I don't like is old-style C which requires you to run a pre-compiler to catch datatype issues. Classic C allowed you to do abominable things with mixed-mode expressions.
On the other hand, P/L-1 is one of those love to hate/hate to love languages where the typing is SO strict that an 80 character string is NOT the same type as a 79 character string and you have to do explicit typecasts to make them work together. But if you get your code past THAT compiler, you KNOW you don't have any datatype issues. Of course, with typical military logic >>cough, cough, choke<<, the Navy decreed about 15 years ago or so that P/L-1 would be the preferred language for all new software development. Fortunately there were waiver processes for compatibility issues. It was always fun to talk about new programs with the Navy. You never knew quite what would be in the specs, but you just KNEW it wouldn't be easy.
I'm a certified grandpa (3 times now) and proud of it.
Retired over one year and survived being home all day with the wife. She must really love me.
If I have helped you, please either click the thanks or click the scales.