For what it is worth, I am with Andy on this. An actual DB, even something simple like SQLite, opens up many additional possibilities while helping to prevent breaking a custom parser.
As he mentioned... this would allow other custom applications written in almost any language to interact with the tool table data. It also allows one to expand the schema and store extra tool information that the mainline LinuxCNC applications might not need but without breaking them. On 10/26/2016 07:53 AM, andy pugh wrote: > On 26 October 2016 at 13:26, TJoseph Powderly <tjt...@gmail.com> wrote: >> >> so >> why not just associate an tool with an index into a technology? > > This has to be part of any solution,because all that G-code knows how > to do is to pass out a single integer, the T-number. > From that point it is down to "something else" to deal with that > number, and currently that is all encoded in iocontrol. [1] > >> and the tech stored in simple ascii flat files. > > This is where we differ, I think. If we are going to expect system > integrators to write custom ways to interpret the T-number then I > think it is actually likely to be easier to have that encoded as a > database query than to write a custom flat-file parser. > Also, you can add your own metadata into a database and a query will > still work with whatever default query LinuxCNC is supplied with. If > you add members to a flat-file (or set of several flat files) then I > think you will break the parser. > > [1] The proposed tool-table changes will almost certainly kill > iocontrol, as then that will only be concerned with coolant and lube > outputs >
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik
_______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
