All,
As I create new operating system independent interfaces it would be best for
them to be placed in a C++ namespace. Currently I have, nested inside the
namespace "epics", a namespace "osi" standing for "operating system
independent". However, perhaps there is some dismay related to the name
"osi", as an acronym for "operating system independent", because it is of
course similar to other acronyms; for example there are of course "open
system interconnect" and "open source imitative" in common use. The name
"osd" is also commonly in use today in the EPICS distribution standing for
"operating system dependent".
Other options:
o epics :: osl - standing for "operating system liberated"
At this juncture, this issue remains quite easy to fix in the source code as
the new namespace is minimally populated.
Comments?
Jeff
______________________________________________________
Jeffrey O. Hill Email [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos NM 87545 USA FAX 505 665 5107
Message content: TSPA
- Replies:
- Re: naming the operating system independence layer Marty Kraimer
- Re: naming the operating system independence layer Ralph Lange
- Re: naming the operating system independence layer Andrew Johnson
- Navigate by Date:
- Prev:
Re: Bug in macLib Andrew Johnson
- Next:
Re: naming the operating system independence layer Marty Kraimer
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
- Navigate by Thread:
- Prev:
Re: Bug in macLib Ralph Lange
- Next:
Re: naming the operating system independence layer Marty Kraimer
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
|