/***************************************************
 ** @author   STF 521
 ** @version  0.0.1
 ** @purpose  1:16.1.4, verify a function called during receiving operation cannot contain a component variable used as an actual inout parameter (in templates)
 ** @verdict  pass reject
 ***************************************************/

// The following requirement is tested:
// If value returning functions are called in receiving communication operations (in templates, template fields,
// in-line templates, or as actual parameters), in guards or events of alt statements or altsteps (see clause 20.2),
// or in initializations of altstep local definitions (see clause 16.2), the following operations shall not be
// used in functions called in the cases specified above, in order to avoid side effects that cause changing the
// state of the component or the actual snapshot and to prevent different results of subsequent evaluations
// on an unchanged snapshot:
// g) Changing of component variables, i.e. using component variables on the left-hand side of assignments,
// and in the instantiation of out and inout parameters (see notes 4 and 6).

module NegSem_160104_invoking_functions_from_specific_places_042 {
    type port P message {
        inout integer;
    }

    type component GeneralComp {
        port P p;
		var integer vc_int := 0;
	}

	function f_inout (inout integer p_inout) {
		p_inout := 1;
	}

	function f_test() runs on GeneralComp return template integer {
		f_inout(vc_int);
		return ?;
	}

    testcase TC_NegSem_160104_invoking_functions_from_specific_places_042() runs on GeneralComp system GeneralComp {
        template @fuzzy integer mw_test := f_test();
        connect(mtc:p, mtc:p);
        p.send(1);
		p.receive(mw_test);
		setverdict(pass);
	}

	control {
		execute(TC_NegSem_160104_invoking_functions_from_specific_places_042());
	}
}
