> On Sun, 22 Mar 2020 at 13:05, Nicklas Karlsson > <[email protected]> wrote: > > > Think the easiest is to increase HAL_NAME_LEN until there is no warnings. > > It feels a little bit ugly but expect it will work without problems. > > Given that user comps or things like mb2hal that pick parts of hal > pin names from the INI file have no real limit to the input string > length, "long enough" is likely to be extremely long. > There are reasonable grounds for limiting the possible length of hal pin > names.
To increase the maximum length must be an easy fix but as you say to upper an upper limit is a problem. Change functions to use dynamic memory allocation on heap, malloc(...) or similar require more work and may introduce memory leaks in case of an error. None of the above solutions are perfect. Ideally then used inside a function programming language would support declaring variables of variable size, then memory would be automatically deallocated at end of function or block there it is declared, it also have an advantage for computer memory could be allocated on stack or with stack like memory allocation which is a choice of compiler. Good for both human and computer. Regards Nicklas Karlsson _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
