{'fraction_non_alphanumeric': 0.025526483726866625, 'fraction_numerical': 0.021059349074664963, 'mean_word_length': 5.348178137651822, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
The applicability of Ada (R) to MIL-STD-1750A

Contrary to recently publicized concern in some DoD sectors, Texas Instruments believes that Ada is a suitable higher order language for the generation of real-time avionics application software on MIL-STD-1750A compatible computers. The perceived problems with using Ada generated programs on the 1750A are not unique to Ada, but also apply to JOVIAL and other high-order languages as well. These perceived problems have been based primarily on subjective, worst-case application scenarios, with no real basis in quantitative, empirical data. Recent analysis internal to Texas Instruments and within the SAE/AE9-E industry/government forum on Computer Architecture Standards have not identified any major shortcomings of the 1750A instruction-set architecture which will present a unique problem for Ada applications. The 1750A architecture has proven to be adequate for many HOL (especially JOVIAL) applications thusfar. The same techniques which have proven successful for applying JOVIAL/1750A to real-time avionics applications will also apply to Ada. These techniques involve an appropriate implementation of the compiler's run-time support model and the observance and enforcement of certain "programming-style" or "coding" methodologies by the application software designer. Furthermore, there is no real evidence to suggest that the techniques which have made JOVIAL usable for past/present real-time avionic applications of 1750A will not continue to apply to foreseeable applications of Ada and 1750A as well.