Re: CATCALLs when running tests via geant

>>>>> "Colin" == Colin Paul Adams <[email protected]> writes:

    Colin> I'm trying to run the xslt tests using geant test_debug_ge,
    Colin> and I'm getting a lot of messages identical to this one:

    Colin> [CATCALL] class TUPLE [NATURAL_32, INTEGER] (ANY,97,8):
    Colin> type 'NATURAL_16' of actual argument #1 does not conform to
    Colin> type 'INTEGER_16' of formal argument in feature `is_equal'
    Colin> in class 'INTEGER_16'


    Colin> as well as many other CATCALL messages.

    Colin> How do I get additional information to try to track down
    Colin> the problems?


Some other the other reported problems appear to be due to the poor
conformance rule for agents. For instance, these messages:

[CATCALL] class XM_XSLT_COMPLEX_CONTENT_OUTPUTTER (417,5): type
'PROCEDURE [XM_XSLT_COMPLEX_CONTENT_OUTPUTTER, TUPLE [XM_XPATH_NODE]]'
of actual argument #1 does not conform to type 'PROCEDURE [ANY, TUPLE
[XM_XPATH_TREE_NODE]]' of formal argument in feature `do_all' in class
'XM_XPATH_EMPTY_ITERATOR [XM_XPATH_TREE_NODE]' 
[CATCALL] class XM_XSLT_COMPLEX_CONTENT_OUTPUTTER (417,5): type
'PROCEDURE [XM_XSLT_COMPLEX_CONTENT_OUTPUTTER, TUPLE [XM_XPATH_NODE]]'
of actual argument #1 does not conform to type 'PROCEDURE [ANY, TUPLE
[XM_XPATH_NAMESPACE_NODE]]' of formal argument in feature `do_all' in
class 'XM_XPATH_NAMESPACE_AXIS_ITERATOR' 
[CATCALL] class XM_XSLT_COMPLEX_CONTENT_OUTPUTTER (417,5): type
'PROCEDURE [XM_XSLT_COMPLEX_CONTENT_OUTPUTTER, TUPLE [XM_XPATH_NODE]]'
of actual argument #1 does not conform to type 'PROCEDURE [ANY, TUPLE
[XM_XPATH_TREE_NODE]]' of formal argument in feature `do_all' in class
'XM_XPATH_TREE_ANCESTOR_ENUMERATION' 
[CATCALL] class XM_XSLT_COMPLEX_CONTENT_OUTPUTTER (417,5): type
'PROCEDURE [XM_XSLT_COMPLEX_CONTENT_OUTPUTTER, TUPLE [XM_XPATH_NODE]]'
of actual argument #1 does not conform to type 'PROCEDURE [ANY, TUPLE
[XM_XPATH_TREE_ATTRIBUTE]]' of formal argument in feature `do_all' in
class 'XM_XPATH_TREE_ATTRIBUTE_ENUMERATION' 

(and more of the same) are coming from this code:

	append_item (a_item: XM_XPATH_ITEM) is
			-- Output an item (atomic value or node) to the sequence.
		do
			if a_item.is_atomic_value then
				if previous_atomic then
					notify_characters (shared_single_blank_string, 0)
				end
				notify_characters (a_item.as_atomic_value.string_value, 0)
				previous_atomic := True
			elseif a_item.is_document then
				a_item.as_document.new_axis_iterator (Child_axis).do_all (agent append_node)
			elseif a_item.is_error then
				on_error (a_item.error_value.error_message)
			else
				check
					node: a_item.is_node
					-- items are atomic values or nodes
				end
				a_item.as_node.copy_node (Current, All_namespaces, True)
				previous_atomic := False
			end
		end
	
	append_node (a_node: XM_XPATH_NODE) is
			-- Output a node to the sequence.
			-- Needed because of wrong agent conformance rule.
		do
			append_item (a_node)
		end

so there is no error (`append_node' will receive an argument that
conforms to XM_XPATH_NODE). Therefore I need to supress these
messages. Is that possible?
-- 
Colin Adams
Preston Lancashire

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/