4 ms·
There is a case for Ada being a fun language to program in. Ada will likely appeal to those who enjoy organization. A fan of Ada will likely have a neatly-ord
by kingmanaz 14y ago
There is a case for Ada being a fun language to program in. Ada will likely appeal to those who enjoy organization. A fan of Ada will likely have a neatly-ordered garage, or if they do DBA work, they will be drawn to the elaborate and tidy typing which C.J. Date demonstrated in his Tutorial-D language. To reuse the garage analogy, simple types will likely appear to those naturally drawn to Ada as unboxed tools or unshelved parts.
Personally I prefer C or Go's approach to typing, eg., use base types (int32, int64, string, etc.) as often as possible or practicable and keep the type hierarchy flat by avoiding multiple-inheritance. Using base types keeps things simple as is reflected in Go's documentation; when descending through documentation for types one can be confident that there is not far to go before hitting a base type. The object is understood.
I do love Ada's use of the range operator (".."), as with it one can simply create 1-based domains and thereby avoid C's omnipresent 0-based domains.
- JulianMorrison 14y agoBase types are just CPU operand categories, it's convenient for the CPU to process numbers in 8/16/32/64/128 bit representations, but those only crudely approximate the domain of a function. It's just nicer to be able to statically say "the volume knob is a real-valued number in the closed interval [0, 11] represented as 32 bit floating point" and have the compiler complain if you even could accidentally assign it the floating point representations of -1 or 12 (which are legal in the CPU type but out of domain for all volume functions).