Re: Restricting instantiation of a nested class to its container
- From: ex-neo-con@xxxxxxxxxx
- Date: 8 Jul 2005 10:12:56 -0700
Hmmm. Doesn't the internal keyword only restrict access to (1) classes
in the same assembly and (2) derived classes in other assemblies?
Thanks for the tip on ListItemCollection. I knew that MS does that in
an umber of places, but I couldn't remember off the top of my head
where. Time to fire-up .NET Reflector!
ex-neo-con
.
- Follow-Ups:
- Re: Restricting instantiation of a nested class to its container
- From: Bruce Wood
- Re: Restricting instantiation of a nested class to its container
- References:
- Restricting instantiation of a nested class to its container
- From: ex-neo-con
- Re: Restricting instantiation of a nested class to its container
- From: Bruce Wood
- Re: Restricting instantiation of a nested class to its container
- From: ex-neo-con
- Re: Restricting instantiation of a nested class to its container
- From: Bruce Wood
- Restricting instantiation of a nested class to its container
- Prev by Date: Re: Parsing HTML
- Next by Date: Re: StreamReader not reading all lines
- Previous by thread: Re: Restricting instantiation of a nested class to its container
- Next by thread: Re: Restricting instantiation of a nested class to its container
- Index(es):
Relevant Pages
|