as i explained you once, i consider this overloading a feature.
Certainly, I remember it, but if you looked well and analyzed the code which I proposed, the overloading is not questioned:
The only thing where I do not agree with you is the order of analysis; according to me the macro which begin by ( ^, $ , ! , ? ) are not to be overloaded in, and on this last point I believe that the majority will be of my opinion.
In your overload of macro, I add simply the possibility of choosing between the macro overloaded by one alias and the macro primary, which I call by preceding its name by one '_', the primary macro '_macro' being priority on quite alias of the same name.
My proposition is not a review but a step furthermore forward while respecting your desires: unless you wish to use the character _ in quite other thing.
if assigned(md.aliases) and not (name[1] = '_') then
//overload macro ....
// ELSEif name[1] = '_' then name:=copy(name,2,MAXINT);
Especially since with your code, one alias of the following chap do not can be overloaded by using the same primary macro,
macroRejetto=macroRejetto|$1|$3|texte1|$2
While with my extension, it is possible to change the order or the quantity of parameters of an existing macro, with no problem at all
In macroMars =_macroMars|$1|$3|texte1|$2
Scripters will have the choice to use or not this possibility without constraint.
[color=red
]I am going eventually rerelease my boxing gloves [/color]
, set
silentpliz as referee and
bacter to count points Very friendly, Mars.