Hi All,

I've scanned through the CR archive and I believe the following have not been
suggested. I'd like your feedback on the following:

* Function Types - i.e. equivalent to being able to pass function pointers
as function parameters, set up variables or arrays of function pointers, or
structures with function pointer fields, etc, etc. This could be used, for
example, to facilitate a some sort of polymorphism, e.g. ability to run the same
test but with different test equipment (e.g. an Agilent signal generator as
opposed to a Rohde & Schwarz one), etc, etc. E.g.:

type function tSetupSigGen ( integer myVal, template myTmplt ) return integer
runs on myMTCType;

function setupAgilentSigGen ( integer myVal, template myTmplt ) return integer
runs on myMTCType { ... }


function setupRSSigGen ( integer myVal, template myTmplt ) return integer runs
on myMTCType { ... }

testcase testTransceiver ( tSetupSigGen setupSigGen ) runs on MTCType { ... }

if ( someoneHasntTakenMyAgilentSigGenToday ) {
testcaseVerdict := execute( testTransceiver( setupAgilentSigGen ) ); } else
{

testcaseVerdict := execute( testTransceiver( setupRSSigGen ) ); }

* Perl Interpretter - a very long shot, but how about incorporating a Perl
Interpretter into TTCN3. The text processing capability of Perl is far superior
to TTCN3 "Matching character pattern" capabilities. Not only that, but
certainly, the Telelogic's implementation is far, far slower than Perl. I've
build the Perl Interpretter into my TTCN3 adaption layer and it's so much better
for parsing MMI info. I guess there are a number of issues up for discussion
here, e.g. Why Perl as opposed to anything else? Legal issues? How to get info
into and out of the Perl interpretter? Etc., etc.


Regards

Ray Cheung


Motorola Inc., Swindon, UK