In order to create a new template operator, the operator definition requires either a 'function' parameter or a couple of 'script'/'class' parameters. The second way is like:

$eZTemplateOperatorArray = array();
$eZTemplateOperatorArray[] = array(
    'script' => 'extension/extName/autoloads/eztemplateautoload.php',
    'class' => 'myOperatorClass',
    'operator_names' => array( ...)
);

But since autoload mechanism is now in charge of loading classes (and class is here stronlgy linked to script parameter), the 'script' parameter should not be needed any more, or at least optionnal.

The methods 'loadAndRegisterOperators' / 'registerAutoloadOperators' in class 'eZTemplate' should then be adapted to fit this new behavior, as it's quite disconcerting for an eZ4 developer to give a full class file path now