project level scope declaration in C#

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Information - 14 Sep 2005 23:10 GMT

Dear Friends,

In VB.NET you can declare something like following..

Module modVar2
Public sb as String
End Module

Now, sb is a project level scope variable and can be accessed any where
in the project.

Similarly I want to do it in C#.NET.

Any help would be appreciated.

Thanks
kdsv

Reply to this Message

Jon Skeet [C# MVP] - 14 Sep 2005 23:20 GMT

> In VB.NET you can declare something like following..
>
[quoted text clipped - 8 lines]
>
> Any help would be appreciated.

public class ModVar2
{
public static string sb;
}

It's generally not a good idea to have actual global variables like
this though - constants, and public static properties are fine, but
variables themselves don't give you much control.

Signature

Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too

Reply to this Message

Brad Bellomo - 30 Sep 2005 21:12 GMT

This is my biggest dislike of C# and Java vs C++, VB and most anything else.

I don't want to see global variable added to C#. However I really really
really would love something in the language that lets me treat static members
and functions of a class as if they were in the current scope.

This is purely for reason of saving the amount of typing I do (both speed of
development, and readability). For example, I want to just type:
x = DoThis(n);
Instead of:
x = MyLibrary.DoThis(n);

If I have a lot of code and frequently use utility functions accross my app,
this really is a lot of typing I have to do in C# that I would not have in
C++. Yes, I know I can just add a function to the class I am working on:

static int DoThis(int x)
{
return MyLibrary.DoThis();
}

but it is a pain to do this all the time for every class and library
function I use often.

How about a feature like putting
using globalscope = MyLibary;
at the top of my class?

> > In VB.NET you can declare something like following..
> >
[quoted text clipped - 17 lines]
> this though - constants, and public static properties are fine, but
> variables themselves don't give you much control.

Reply to this Message

Jon Skeet [C# MVP] - 30 Sep 2005 22:24 GMT

<=?Utf-8?B?QnJhZCBCZWxsb21v?= <Brad
Bellomo@discussions.microsoft.com>> wrote:

> This is my biggest dislike of C# and Java vs C++, VB and most anything else.

Well, Java 1.5 has import static which does exactly what you're after.
In my experience it's handy in certain situations (particularly for
enums), but shouldn't be used particularly often.

Signature

Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

Reply to this Message

Mattias Sjögren - 14 Sep 2005 23:32 GMT

>Similarly I want to do it in C#.NET.

Just add a public static field or property to class. The only
difference is that you have to include the class name to reference the
member, it will not auto-import like VB Module members do.

Mattias

Signature

Mattias Sjögren [MVP] mattias @ mvps.org
http://www.msjogren.net/dotnet/ | http://www.dotnetinterop.com
Please reply only to the newsgroup.

Reply to this Message

Information - 15 Sep 2005 14:21 GMT

Thanks a lot guys.

Reply to this Message

project level scope declaration in C#

Free Magazines