My source lives under a src/ folder which contains subdirectories each tied to the canonical dotted package name portion. This is like in java.
Example:
Package Name: mycompany.product.technology.component
File System: src/mycompany/product/technology/component/
I'd expect some magic like the +package.dottedname+
Proposal:
+functionname:param1,param2, paramN+
Example:
+split_on('.', package.dottedname)+
This would need a preprocessing phase for the template variables.To distinguish functions even more from plain variable substitutions you could use another prefix or an another like:
$split_on('.', package.dottedname)$
+%split_on('.', package.dottedname)%+
%split_on('.', package.dottedname)%
or mor lisp like with prefix notation:
+(split_on '.' package.dottedname)+
$(split_on '.' package.dottedname)$
%(split_on '.' package.dottedname)%
This would have to advantage of being easier to parse. The first parameter after the opening bracket is the function name and the rest are the parameters. Or you just use pythons evel to do the function evaluation without further parsing and supplying the variables and args.
This would need some basic functions supplied like the split_on and provide new or unknown ones in the hook.py from the package used.
My source lives under a src/ folder which contains subdirectories each tied to the canonical dotted package name portion. This is like in java.
Example:
Package Name: mycompany.product.technology.component
File System: src/mycompany/product/technology/component/
I'd expect some magic like the +package.dottedname+
Proposal:
+functionname:param1,param2, paramN+
Example:
+split_on('.', package.dottedname)+
This would need a preprocessing phase for the template variables.To distinguish functions even more from plain variable substitutions you could use another prefix or an another like:
+%split_on('.', package.dottedname)%+
%split_on('.', package.dottedname)%
or mor lisp like with prefix notation:
$(split_on '.' package.dottedname)$
+(split_on '.' package.dottedname)+
%(split_on '.' package.dottedname)%
This would have to advantage of being easier to parse. The first parameter after the opening bracket is the function name and the rest are the parameters. Or you just use pythons evel to do the function evaluation without further parsing and supplying the variables and args.
This would need some basic functions supplied like the split_on and provide new or unknown ones in the hook.py from the package used.