public static : inaccessable due to protection level!?

[MushroomStamp]

If a member of one class is public static, what protection level does it have and how can you grant other classes acess to it? I would have expected the public-ness of it to suffice general reading priveleages to any class using the same namespace. What is wrong with my thinking?

[TheCPUWizard]

Assuming the CLASS is public....nothing is wrong with your thinking....just with your doing...Please post a minimal / compilable snippet of code that exhibits the problem.

[MushroomStamp]

namespace Logging
{
	public class CQuickLog
	{
		public static string	CLX_LOGFILE	= "Clx_log.txt";
		public static string	PLX_LOGFILE = "Plx_log.txt";
		
		CQuickLog(string sPlatform)
		{
			//...
		}

	}
}

and within other class

using Logging;

...
CQuickLog m_QuickLog;
...
m_QuickLog = new CQuickLog( CQuickLog.CLX_LOGFILE );

[TheCPUWizard]

The access problem is on the constructor, not the static!

   string s = CQuickLog.CLX_LOGFILE;  // OK
   CQuickLog ql = new CQuickLog( s);  // Fails

[MushroomStamp]

why? does it assume that the constructor might try to change the value of the string?

[MushroomStamp]

WOW, sorry about that. i forgot to make the constructor public. i'm too used to c++.

[MushroomStamp]

Just another thought...

Why don't c# ctors default to public? I've always thought of private ctors as just a shady means of enforcing abstractness...

[TheCPUWizard]

Not at all....Consider the following to enforce parameter checks

public class C
{
   private C(int x) {...}
   public static C Build(int x)
   {
      if ((x%2)  == 0) return new C(x) else return null;
   }
}

..elsewhere..
C a = C.Build(3);   // Will return NULL;
C b = C.Build(2);   // Will return an instance;

disclaimer...not responsible for typos, this is only a sample....