Should MyType's synthetic provider be instantiated for MyType* and MyType** ?

Hi,
I am observing that if I bind a synthetic provider to MyType, it will also be instantiated for MyType*, MyType**, etc, and the object passed into the constructor will be of the pointer type. I’d have expected the synthetic to either not be instantiated for pointers, or to be constructed on the pointee object directly.

Is this a bug or done this way on purpose?

You can control whether you want data-formatters on "class Foo" to also match "class Foo *" and "class Foo &" using the --skip-pointers and --skip-references options respectively.
So this part is clearly is by design.

As for what the formatter gets passed, your formatter has chosen to see values that are pointers to the type by not passing --skip-pointers, so it makes sense to pass it
the pointer - which it after all asked for. I can't see a strong enough argument either way to want to change the way it currently works, since we might break other people's uses of it.

Jim

Certainly. I just wish the documentation were more explicit about this quirk. This behavior is especially confusing because the single indirection case usually works, since pointer.GetChildMemberWithName(’…’) transparently dereferences. It starts breaking only at pointer-to-pointer-to-type.

You can control whether you want data-formatters on "class Foo" to also match "class Foo *" and "class Foo &" using the --skip-pointers and --skip-references options respectively.
So this part is clearly is by design.

As for what the formatter gets passed, your formatter has chosen to see values that are pointers to the type by not passing --skip-pointers, so it makes sense to pass it
the pointer - which it after all asked for. I can't see a strong enough argument either way to want to change the way it currently works, since we might break other people's uses of it.

Certainly. I just wish the documentation were more explicit about this quirk. This behavior is especially confusing because the single indirection case usually works, since pointer.GetChildMemberWithName('...') transparently dereferences. It starts breaking only at pointer-to-pointer-to-type.

Feel free to add something you would have found helpful to the documentation.

Jim