/***************************************************
 ** @author   STF 521
 ** @version  0.0.1
 ** @purpose  1:16.1.4, verify that the map operation cannot be used in guards of altsteps
 ** @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:
// b) All port operations, i.e. start (port), stop (port), halt, clear, checkstate, send, receive, trigger, call,
// getcall, reply, getreply, raise, catch, check, connect, disconnect, map and unmap (see notes 1, 2, 3, 4 and 6).

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

    type component GeneralComp {
        port P p;
	}

	function f_test() runs on GeneralComp system GeneralComp return boolean {
		map(mtc:p, system:p);
        return true;
	}

    altstep a_rcv() runs on GeneralComp system GeneralComp {
        [f_test()] p.receive(integer:?) {}
    }

    testcase TC_NegSem_160104_invoking_functions_from_specific_places_237() runs on GeneralComp system GeneralComp {
        connect(mtc:p, mtc:p);
        p.send(1);
		disconnect(mtc:p, mtc:p);
		a_rcv();
		setverdict(pass);
	}

	control {
		execute(TC_NegSem_160104_invoking_functions_from_specific_places_237());
	}
}
