On 3/29/26 3:31 AM, Chris Morley wrote:
A good portion of INI entries are parsed by python directly. We
would need to check if any of the rules are bent there. One rule i
think that's bent is finding multiple entries under one heading that
are the same spelling. Another is getting all the entries under one
heading as a list.
I think (hope) most python ini parsing is done through the ini-interface in module linuxcnc.ini (emc/usr_intf/axis/extensions/emcmodule.cc). This will simply invoke the new parser. But I still have to go through all the front-end code to fix consistency things.

The reason for creating the new parser was the complete lack of consistency when reading boolean values (see https://github.com/LinuxCNC/linuxcnc/issues/3863).


I dont think we restrict the entry name at all. I would need to check if pythons configparser has default restrictions.
Good point. I'd also need to check where/if it is used and how it behaves. A real problem might be different syntax behaviour. Especially string handling. Also, it probably does not support includes, which is now part of the parser.

If there are any instances of /other/ ini parsers used in the code, then they need to be changed to the LinuxCNC version. It is a real pain to use different parsers and expect consistency, which was the problem in the first place...

--
Greetings Bertho

(disclaimers are disclaimed)



_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to