{'fraction_non_alphanumeric': 0.011111111111111112, 'fraction_numerical': 0.0, 'mean_word_length': 4.91970802919708, '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}}
Message conversion and a new type system for OO model

In this paper, we propose that the messages should be defined independently to the class definitions in an object-oriented program. The compatibility relation between two message types is also discussed. This kind of relationship is essential and useful for software reuses. A software designer can declare the compatibility relation between two message types if messages are defined independently to the class definitions. A message of one type can be converted to another type automatically when necessary if a compatibility relation between the two message types is specified. A new type system is proposed based on these new concepts in this paper. This type system is more flexible than the traditional ones while keeping the safety of type checking.