Im not against recursion at all, Im just against the status quo being altered, I dont consider an -r switch altering the status quo tho, as thats an extention, and would be fine with that, in fact bring it on!, I was going to mention duplicating the alias and calling the other one (which i do find pretty a repulsive idea personally) as the method to up the count to 1000, but really I feel that if you know how many recursions your going to need or suspect that depth is needed then you likely know you should be looking to do it another way, something flat which keeps its own stack table.
My only gripe on "recursion/alias's calling themselfs" is currently an alias cant call itsself FINE why cant it call another alias called the same thing!
ie:
I write
alias msg { msg $1 Attention message from $me follows $$2- }
^ Thats fine it works.
But what if there is also an alias present (maybe in some addin script) such as
alias msg { var %text | scon -r var $+(%,text) = $+(%,text) $!+($upper($left( $* ,1)),$mid( $* ,2)) | msg %text }
^ this well never get processed
* I really find being able to replace a comand with an alias helpfull, but i dont find its helpfull to not be able to allow other scripts access to the command after mine.
Assuming this was done it would not need to cause recursions back into the first script, becuase it could be riggered that it only scans from the current script downward for a identical name alias, since any before it have already been run once., this would be supperseeded by an -r switch which says run myself if i call myself ect.
** I have actually built a workaround for this problem so i dont actually need anything changed, but i just felt it would be nice as well.
