You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Earlier, the NGen had it's Managers define a static buffer in their header files which was attempted to be handled in the implementation, this of course led to errors and many warnings.
In an attempt to cull all warnings, the Managers are temporarily being given an external linkage to a buffer defined in the implementation.
This however renders the GetBuffer functions useless. We must decide if we want a static variable defined only in the implementation which can be accessed by reference through a function, or to just maintain public external linkage through the header (in which case the GetBuffer functions should be removed).
The text was updated successfully, but these errors were encountered:
Earlier, the NGen had it's Managers define a static buffer in their header files which was attempted to be handled in the implementation, this of course led to errors and many warnings.
In an attempt to cull all warnings, the Managers are temporarily being given an external linkage to a buffer defined in the implementation.
This however renders the GetBuffer functions useless. We must decide if we want a static variable defined only in the implementation which can be accessed by reference through a function, or to just maintain public external linkage through the header (in which case the GetBuffer functions should be removed).
The text was updated successfully, but these errors were encountered: