On 5 November 2013 09:34, Michael Haberler <[email protected]> wrote:
> I have created a document describing the HAL remote component protocol
> design, overview, and specification based on zeroMQ sockets and protobuf
> messages.
This sounds interesting, though seems like a lot of work for what may
be a rather rare usage case.
I mention this as it recently became obvious that nobody has ever, in
the history of the world, run a VW-plane canned cycle in LinuxCNC. Is
there a danger here of adding a feature that never gets used?
(Probably not in this case, as we have seen enquiries about how to do
this).
One issue is that the NIST design is very specific that only one thing
can ever change another thing, ("NIST logic") and you are proposing to
change that. I am not sure that is a bad thing (and could be a very
useful thing) but I would like to understand the logic behind the NIST
policy.
Curiously, I can't find any definition of "NIST logic" so might have
completely the wrong end of the stick.
--
atp
If you can't fix it, you don't own it.
http://www.ifixit.com/Manifesto
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
