hal: Migrate homecomp is_module pin declaration to bool - #4329
Conversation
Leftover from f107cd3: the is_module dummy pin was still declared with the legacy bit type while the rest of homecomp uses the new getter/setter API.
|
The build is filtered out in the Submakefile together with tpcomp.comp. These are supposed to be examples of plug-able homing and TP. Neither works in practice or has never been tested to be actually functional afaik. Both modules need to hook into a lot of internals and that is quite contrary the modularization idea. But sure, we still need to update it, even if it doesn't fix things ;-) |
|
This is all that came up, while re-reviewing looking for sets before create, that's a good sign... |
Yes it is! And, have you noticed, no one complained about breakage :-) |
Note that 'homecomp.comp' has definitely been used and has been proven to work. 'tpcomp.comp' on the other hand has apparently proven less useful. |
|
Interesting... WRT tpcomp.comp, this should be removed IMO. The first refactor step is to get TP moved out of RT and make a formal TP input/output specification that can be exposed. Then we can have proper plug-able TPs. However, moving it out of RT is a big undertaking and a lot of work. |
If it is to be removed then we'll want to also remove it from the documentation: linuxcnc/docs/src/config/ini-config.adoc Lines 687 to 690 in ddd8aef |
|
We could also fix it :-) But that will take some time. Besides, we'd need a real example to add, not a mostly empty shell. |
That would be very much my preference. :) |
One leftover from the getter/setter migration: homecomp.comp still declares its dummy
is_modulepin with the legacybittype, while the rest of the component was migrated in f107cd3 (#4296).Found with a tree-wide
halcompupdate --checksweep (from #4256) against current master; this was the only genuine declaration leftover among all in-tree .comp files not already covered by open migration PRs.Change:
pin out bit is_module=1=>pin out bool is_module=1. Builds clean.