>>Hmm, not 100% sure about that. Is there not still a dependency on the parameter object i.e. its (continued) existence, that it remains in scope/doesn't end up dangling etc. ?
>
>Those all 'made up problems' not real ones for a parameter object

Parameter objects are passed by reference. The temptation is for Child.Init() to simply store that reference somewhere (because that's easy), then use that to access the passed properties. If at some point the original parameter object disappears, but after that the child needs to access its properties via the stored reference, what happens then?

Yes, this can be avoided by the child storing the individual parameter object properties, at which point the object reference can be discarded. But that takes extra work and isn't obvious.

>>If you truly want to pass in parameters once and have them stay the same in the child, with no dependencies, the cleanest is probably to pass them as straight byval parameters.
>
>It's not. The parameters are passed in VFP by position so there's no way to know or verify that you are getting what you are expecting

Sanitizing input parameters is a different question, and needs to be done however parameters are passed.