>>>I don't see the point of hiding the code either. ?
>>
>>It's not our practice to tell you, but in an organization wherein code is a top secret, there's no point of argument why to hide codes? Besides, the point is, there is a trick how to achieve it without affecting the functionality of the said classes.
>
>Sad but true observation - the people who live in areas not supporting the concept of IP and most willingness to pirate software are the ones who want to hide their source!

Ed,

Hmmm...sort of a controversial statement. While we don't practice hiding source code, it is only within our organization. We sell and install custom-made software without source codes. If our client want the source codes it's a separate deal and to tell you it's even more expensive than the application itself. In anyways, we are using a tool (VFP) in which codes are vulnerable for piracy because it does not support true compiled code. Besides, there is a REFOX available.

We don't hide source code within the organization with the following reasons:
1. we want our programmers to see the actual interpretation of the documented SAD into program code.
2. functional codes are the most qualified when it comes to standardized programming and so it plays as a model for them to follow (although we have a seasonal separate technical session discussing 'standard programming within the organization')
3. while our source codes are exposed within the software division, not every PC had external drives or any external storage devices. We have a common PC for releasing purposes only.

In our country, it's hard to totally eradicate piracy but it has been minimized with the effort and cooperation of Business Software Alliance members.

Hope my statements does not sound like we are guilty of piracy... :)