What happens when you don't nameProcessGuess()'s FString parameter?

[3zer]

Firstly I want to confirm if I’m correctly understanding how the parameters and arguments work.

When the code compiles and sees ‘Input’ passed through as an argument for the ProcessGuess() function, because it’s a string it then redefines it as ‘Guess’ within the scope of the ProcessGuess() function?

If that is the case, if you don’t redefine the FString ‘Guess’ at all, and leave it like this:

How would you refer to ‘Input’ in the function? Would you just type ‘Input’ instead?

Secondly, in the header file, ‘Input’ is included as a parameter for the ‘OnInput()’ function ,

so why doesn’t it work when it’s used as a parameter for ‘ProcessGuess()’?

[DanM]

@3zer

because it’s a string it then redefines it as ‘Guess’ within the scope of the ProcessGuess() function?

It’s essentially doing FString Guess = Input when you call the function.

@3zer

How would you refer to ‘Input’ in the function? Would you just type ‘Input’ instead?

You can’t

@3zer

Secondly, in the header file, ‘Input’ is included as a parameter for the ‘OnInput()’ function ,

It’s not used at all in the declaration. You don’t even have to name parameters in a declaration. However It comes up in tooltips so it’s preferable if you give it a name so users can see what should be entered there. Seeing a list of types isn’t going to help anyone e.g.

void DrawDebugLine(const UWorld*, FVector const& , FVector const&, FColor const&, bool, float, uint8, float);

Seeing that come up in autocomplete is not helpful.
vs what Unreal actually has

void DrawDebugLine(const UWorld* InWorld, FVector const& LineStart, FVector const& LineEnd, FColor const& Color, bool bPersistentLines = false, float LifeTime = -1.f, uint8 DepthPriority = 0, float Thickness = 0.f);