{'fraction_non_alphanumeric': 0.020804438280166437, 'fraction_numerical': 0.0027739251040221915, 'mean_word_length': 5.333333333333333, '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}}
Relationship between the standard compliance of IDL-compilers and interoperability of CORBA-based applications

Ever since the introduction of version 2.0 of the CORBA specification, that architecture enjoys ever-increasing popularity. There are two reasons for this, both due to the underlying principles of CORBA - easy interoperability between different ORB products and the possibility of cooperation with other (sub)systems. However, for the first advantage to come to bear, it is paramount that the IDL specification is accurately implemented by the ORB products. In this paper we examine the IDL compilers of different ORB products with regard to standard compliance and discuss the problems arising from deviance.