Dynamically created signal patchcords won't pass signal, alternatives to JS?

    Jan 30 2019 | 11:24 pm
    This seems to have been an issue for many years as this topic shows: https://cycling74.com/forums/dynamically-created-patchcords-made-with-js-wont-pass-signals
    The (0, 1) message to a dac~ object (both dac~ and ezdac~) will not alter this behaviour.
    I would really appreciate some help with this issue, however due to the seemingly longstanding nature of this, I'd like to know if this is an documentated limitation of JS in Max, or is it still a bug?
    If it is just a limitation then I'd like to know if there are any more workarounds, but if it is a bug I'd like to know if there are any alternatives to dynamically creating objects and routings inside of Max? Particularly if it involves textual programming as I am more comfortable with programmiing in text.
    If anyone wonders why I created a new topic for an issue that already has a topic - I felt that asking about alternatives was offtopic on the existing post, plus it is nearly 7 years old at this point.
    Any help would be greatly appreciated!
    Many thanks, James :)