Closed adamkewley closed 8 months ago
Fixes having to use a try {} catch (...) {} to find a socket/output on a Component.
try {} catch (...) {}
tryGetSocket
tryUpdSocket
tryGetOutput
tryUpdOutput
Component
try
nullptr
try...catch
getOutputs
This change is
Note: can't merge this until I ensure the manual merge commit was ok: there are merge conflicts related to adding list sockets to parts of the API that this PR also touches (line-wise: functionally, not).
Fixes having to use a
try {} catch (...) {}
to find a socket/output on a Component.Brief summary of changes
tryGetSocket
,tryUpdSocket
,tryGetOutput
, andtryUpdOutput
to theComponent
interfacetry
, because they will returnnullptr
if the socket/output cannot be found on the componenttry...catch
or allocating memory (e.g. withgetOutputs
) and searching in downstream codeTesting I've completed
CHANGELOG.md (choose one)
This change is