🚀 go-pugleaf

> ==> Guo_Wu(Alight)                           ˵��: 
> VC����һ������������������Դ�ļ������� 
> ��ͬ�ı�����Ļ�,���������Dz�������,���� 
> Ҳû�о���.��������ʱ,�����������ĵ�ַ���� 
> ��ͬһ�������ַ��.��ͻ�����һЩ����,��Ϊ 
> ���DZ���ϣ������������ͬ�ı���. 
> ��Ϊ��Ҫ���һЩ��̬���ļ�,����б��뱣�� 
> һЩȫ�ֱ���,Ϊ�˷�ֹ���ú�����ҵ��ļ��� 
> ȫ�ֱ����ĸ���,������Ӧ�ò�ȡ���ַ��������� 
> ������Щ����.��Ȼ�Ҳ������ڿ��н��������� 
> ��static��,��Ϊ�ļ�ʵ��̫��,�����ڲ�ͬ�ļ� 
> �ж���Ҫ������Щȫ�ֱ���. 
> лл�����. 
Yeah, It's a problem.  I don't know how to do it.  Indeed, if you
compile this package into a DLL, you can control what will be exported.
But I don't know any method to control the exports of standard LIB.
In fact, there are only two kinds of global variables: static and extern.
And if you really want to share the variables among your source files(
a bad habit), I think you can use a very long name to avoid the problem.
Or you could try this:
	class MYLIBVARIABLES
	{
		static int var1, var2;
	}
There is only little chance to the user program to use this class name. 
 

--
�� ��Դ: �й�ƴ�BBSվ [bbs.ustc.edu.cn]