1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 <2007> 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: error code mapping best practice |
From: | Maren Purves <[email protected]> |
To: | "Rodney R. Porter" <[email protected]> |
Cc: | [email protected] |
Date: | Tue, 10 Jul 2007 17:04:54 -1000 |
void dhsDhsErrHd (int status) { char string[DHS_STRING_LENGTH];
lying around. This runs on an IOC and is part of the 'device support' for FITS files - obviously you can extend the number of codes to any enum value.
If I was to do this again today I'd probably put it into a table (hopefully pvLoad-able) and use a genSub (I think the code above predates genSubs, at least it predates genSubs being wide-spread).
Aloha, Maren
I have implemented similar conversions, though with considerably less than 300 states, using either a genSub record or SNL program. I choose between them based on what is needed for other support for the device or instrument. Rodney Porter
On 7/9/07 4:38 PM, "Emmanuel Mayssat" <[email protected]> wrote:
Hello, I have a device that returns error codes as integers (error code stored in a ai record). The error codes needs to be mapped to the corresponding strings. I have approximately 300 error codes. What would you say is the most elegant way to implement the translation? Custom record? seq? etc.
Thank you for your advice, -- E