[osg-users] DEEP_COPY_USERDATA isn't that deep

Robert Osfield robert.osfield at gmail.com
Tue Sep 24 10:11:41 PDT 2019

Hi Chris,

On Mon, 23 Sep 2019 at 17:33, Chris Djali <krizdjali at gmail.com> wrote:

> Good, but would the new enum entry be for the current behaviour or the new
> behaviour? If the current behaviour is a bug, then it makes sense to only
> keep the old behaviour as the new enum value so everyone gets the fix, but
> conceivably there could be applications that rely on the current behaviour
> not changing, so would want the same name and value to keep the same
> behaviour.

Relying upon buggy behavior is always a dangerous thing, especially if you
don't know about it.

Unfortunately there is no easy way to know whether there are any
applications that are relying upon buggy behavior.  Given UserData is a
relatively niche feature I think we are probably not taking too much of
risk with fixing it's behavior.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20190924/689d1c54/attachment.html>

More information about the osg-users mailing list