Add a New Comment (Rich Markup)
similar issues seem to be with FORMAL_GENERIC_TYPE_MARK.class_text. I agree, that these seem to be not intended to be called, but isn't there a cleaner way to design this? Or at least formulate a nice precondition, which forbids calling class_text and try_class_text for non-static-type marks?
class TYPE_MARK has the feature try_class_text: CLASS_TEXT require not is_anchored not_done_to_report_errors: error_handler.is_empty local bcn: CLASS_NAME do if class_text_memory = Void then if not has_tried_to_load then bcn := class_text_name if bcn /= Void then Result := bcn.try_class_text class_text_memory := Result end has_tried_to_load := True end end For its subclass FORMAL_GENERIC_TYPE_MARK class_text_name is Void and therefore if bcn /= Void then will never be True. NON_STATIC_TYPE_MARK.class_text_name has a check False end in it by the way, so there seem to be some unexpected call here...
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 3 latest changes.
Copyright © 2023 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.12