BabaJ
Soothsayer
-vex wrangles should have an additional text box where we can define functions to be used later in the main code.
You can do that with #include <textfile_with_your_functions.h>
Includes are a possibility but in the spirit of Quality of Life here are the problems as I see them:
-dependency management: includes becomes a dependency of the main code file and it's associated houdini version and you need to manage dependencies and track changes to the code. Name collisions will also occur and be dealt with.
-code clarity: the included file either contains a large amount of code, which makes it difficult to read and understand or you end up with countless artist supplied files.
-accessibility: if you are in a studio environment permissions and potentially file structures need to be set up and approved. Pipeline might want to get involved and cause much delay and overhead.
-debugging: tracking down problems, especially if they happen to the farm or more junior users become more complex. If pipeline insists on version controlling the code then it deters artists from using includes.
Defining and using new functions in VEX can and should really be straight forward. There's no need to open a can of code management worms if all you want is organizing your own little wrangle backyard.