I've been drilling into a lot of Matlab recently trying to interface with an in house algorithm engineer's work to modularize it for use in a test bench outside his suite of applications. I've come across several links from several different areas and concepts that connect to this undocumented MATLAB website.
I've been hesitant to dive into any solutions proposed there since I've always been taught not to rely upon undocumented behavior, since well it may be deprecated and is generally subject to change. I suppose however for the sort of software that would be developed in MATLAB such implementation shake ups wouldn't bring too large of a house crumbling down to be refurbished, but I was curious is there something to the way Mathworks develops that they manage to allow so many hooks into their undocumented architectures and frameworks? What could be preventing them from formalizing these things.
Just as a concrete example while researching UI layout techniques for programmatic GUI creation one of their articles made mention of this
uiflowcontainer, which if you get the documentation on it you find it is undocumented.
>> help uiflowcontainer This function is undocumented and will change in a future release
In general I find it very curious and amusing that such a development tool has built such a following to its undocumented internals. Any thoughts on that reality? Is it foolish, crafty, or something in between?