I faced the same issue a couple of years ago. The company I work for was
called FDS so this was used in all the class names we created. We were sold
and now trade under a new name. I decided to stick with FDS in existing and
new code as this would be less confusing.
Mike
On 21 May 2012, at 01:22, Przemek Klosowski <przemek.klosow...@gmail.com> wrote:
> On Sun, May 20, 2012 at 6:56 PM, Dave <e...@dc9.tzo.com> wrote:
>> On 5/20/2012 6:13 PM, gene heskett wrote:
>>> On Sunday, May 20, 2012 06:11:51 PM charles green did opine:
>
>> I also don't see any sense in going into the source code and changing
>> all references of "emc" to something else.
>
> OK, but then should we also keep using 'emc' in new code? or start
> using the new term? The latter seems confusing, especially as it could
> end up in 'struct emc_xxx { int LinuxCNC_yyy..}. It's not a big deal,
> just have to decide on something.
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
