Just had a thought about the canon layer. It would be really nice if
CANON_POSITION was unit-aware:
typedef struct {
double axis[9]; (or just 9 doubles)
unit_t lin_unit;
unit_t ang_unit;
} CANON_POSITION;
unit_t would be an enum representing each known unit (in, mm, deg, rad,
sec, cm, whatever).
Explicitly storing a unit would mean that arithmetic operators could
automatically scale units, and unit conversion could be done as a class
method. It might be slightly less efficient in CPU terms, but it would mean
that the plethora of FROM_EXT_LEN macros in canon and elsewhere could
disappear, and make writing canon-level operations way simpler.
Ignoring the labor involved in doing the conversion, does this sound like a
good idea?
Thanks,
Rob
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
