Variables as variable defaults don't work

Question

Variables as variable defaults don't work

Opened this issue 8 years ago · 8 comments

Alkali-Metal commented 8 years ago

What is the issue?

When you put a variable as the default for another variable, it doesn't work, it returns the variable as it is.

How do we reproduce this issue?

Do that.

Environment

Remote hosted CactusBot 0.4

Other Information

I feel as though it should work because it would make default arguments much coolio-er. 😄

Also: default arguments for %ARGS% doesn't work, it returns Not enough arguments

Answer 1 · 2017-03-30T02:42:42.000Z

Hmm... this wasn't really considered. Could look into it, just making sure that recursion isn't an issue. 👍

Answer 2 · 2017-03-30T02:43:50.000Z

Yeah, that would be a mild issue. XD

Answer 3 · 2017-05-06T03:36:51.000Z

Fixed this in #295

Answer 4 · 2017-05-06T03:41:07.000Z

Silly @Innectic. ;P

Answer 5 · 2017-05-06T16:21:56.000Z

Can confirm, am noob.

Answer 6 · 2017-05-12T02:21:32.000Z

You Innectato!

Answer 7 · 2017-05-27T06:33:01.000Z

So, I was thinking about this, and I would that only having one layer-o'-recursion would be fine, anything beyond that would just be pointless and redundant in my opinion.

One layer:   %ARGS=%NAME%%           #Would work
Two layers:  %ARGS=%ARG1=%NAME%%%    #Wouldn't work

If that makes any sense.

And it should check to see if they are the same so that it can't do something like %ARGS=%ARGS%%

Answer 8 · 2017-05-29T20:31:30.000Z

I would agree; having more than one layer doesn't really make sense.

The more I think about it, the more I think recursion might not be an issue... for example, with the response %ARG1=%ARG2%% %ARG2=%ARG1%%:

If no args, error message.
If only %ARG1% as a, response is a a.
If also %ARG2% as b, response is a b.