ID 475753 - Output port parameters added to an OSL shading node can be out of order

Problem summary

Output port parameter an OSL shading node can appear out of order on the node after addition.

This appears to only affect nodes in the NMC/NME context.

Customer reported version
Katana N/A

Customer reported platform

Steps to reproduce

Rquirements: 

OpenShadingLanguage

RenderMan (Specific to these reproduction steps)

1) Create a new directory named shader

2) Define the RMAN_SHADERPATH environment variable with the shader directory path as the value

3) Download the attached CustomShadingNode.osl file to the shader directory

4) Compile CustomShadingNode.osl by using oslc in the terminal: oslc CustomShadingNode.osl

(On successful compilation it will produce a CustomShadingNode.oso file in the shader directory)

5) Launch Katana with RenderMan

6) Create a NetworkMaterialCreate node and jump inside

7) Create a CustomShadingNode and set the edit flag

8) Edit CustomShadingNode.osl, adding a new output above the others (be sure to give it a unique name)

9) Save your changes and recompile CustomShadingNode.osl using the same command as step 4

10) In Katana select Util > Reload Shaders and Args Files

Expected behaviour
The port order adheres to what is defined in the OSL shader. 

Actual behaviour
The ports are not in the order defined in the OSL shader

Workaround
Recreate the shading node

Reproduced by support

This bug has been reproduced in:
Katana 4.0v4 - Windows 10

Katana 4.0v1 - Windows 10

Katana 3.6v4 - Windows 10

Katana 3.6v1 - Windows 10

Earliest version tested

Katana 3.5v4 - This issue doesn't appear in this version and has regressed