Default values for member variables

[WouterWeynants]

Right now the docs cannot generate when you declare a default value on classes, struct, etc their member variables:

UPROPERTY()
float MyValue = 1.f;

This is probably intentional as a design decision since it may be prudent to only rely on constructors in the .cpp to set default values, a good habit but not one many stick to. I would love to hear your thoughts about either changing the docs plugin to ignore (and at least not fail building documentation) in these cases and why specifically none of your example code (and systems architecture code) ever sets a default value in the header? Is it just a good things to do to maintain clear and well structured code?

Thank you in advance,
Wouter

[WouterWeynants]

Same thing with a lot of common header code, I'll post any I encounter. Virtual destructors fail too, subclassing from FRunnable, probably happens with others too:

	virtual ~FMyRunnable() override;

[WouterWeynants]

For now I've been keeping things outside of headers as much as possible, or wrapping things in //// [ignore] blocks but it feels wrong as a long term solution

[PsichiX]

oh yeah, the default values parser is at the moment very simple, this one has to go through some heavy lifting, i've encountered this too in more day-to-day work.
that one would require some more work so i wouldn't expect it to happen in a week sadly, rather something closer to a month since i would have to basically add c++ expressions parser, or at least figure out clever way to parse it as a token sequence rather than ast, which might be somewhat hard with PEG parsers.

[B1ackg0d]

Right now the docs cannot generate when you declare a default value on classes, struct, etc their member variables:

UPROPERTY()
float MyValue = 1.f;

This is probably intentional as a design decision since it may be prudent to only rely on constructors in the .cpp to set default values, a good habit but not one many stick to. I would love to hear your thoughts about either changing the docs plugin to ignore (and at least not fail building documentation) in these cases and why specifically none of your example code (and systems architecture code) ever sets a default value in the header? Is it just a good things to do to maintain clear and well structured code?

Thank you in advance, Wouter

Right now the docs cannot generate when you declare a default value on classes, struct, etc their member variables:

UPROPERTY()
float MyValue = 1.f;

This is probably intentional as a design decision since it may be prudent to only rely on constructors in the .cpp to set default values, a good habit but not one many stick to. I would love to hear your thoughts about either changing the docs plugin to ignore (and at least not fail building documentation) in these cases and why specifically none of your example code (and systems architecture code) ever sets a default value in the header? Is it just a good things to do to maintain clear and well structured code?

Thank you in advance, Wouter

Hello, it is the correct thing to set default values for member variables in UE, otherwise, when building the Shipping package in UE, any member variables that do not have default values will be random values.