https://wiki-ext.aps.anl.gov/epics/index.php?action=history&feed=atom&title=Conversion_Code_Clean-Up 2026-06-05T08:05:39Z Revision history for this page on the wiki MediaWiki 1.36.1 https://wiki-ext.aps.anl.gov/epics/index.php?title=Conversion_Code_Clean-Up&diff=2921&oldid=prev 2010-10-18T16:25:30Z

<p>First version of Conversion Code Clean-Up description</p> <p><b>New page</b></p><div>== Conversion Code Clean-Up ==<br /> <br /> === Current Situation ===<br /> <br /> There are two codes for conversion, a full version in '''db/dbConvert.c''' and a &quot;fast&quot; version in '''db/dbFastLinkConv.c'''.<br /> <br /> Both contain the full matrix of conversions as a large set of almost identical C functions.<br /> <br /> === Possible Improvements ===<br /> <br /> Using templated functions in C++ would greatly reduce the source code, still allowing for source level optimization by providing explicit instantiations for simple cases (e.g. same type).<br /> <br /> The new functions could also be changed to not use dbAddr as parameter (explicitly name the parts needed from dbAddr instead), so they can be used for non-V3-record applications.<br /> <br /> The array interface could be improved:<br /> * Start/End/Increment parameters would allow extracting sub arrays<br /> * Chunked array storage could be supported<br /> <br /> === Approach ===<br /> <br /> First step should be adding test code that verifies all conversions, and takes performance numbers. That way the existing code could be tested for both function and performance.<br /> <br /> Then, the new conversion routines should be implemented, with simple wrappers that map the existing (array of function pointer) interfaces to use the new code.<br /> <br /> The test code should be used to verify and spec the new implementation.</div>

RalphLange