On Fri, Dec 12, 2014 at 03:04:21PM +, Paul via Digitalmars-d-learn wrote:
> On Thursday, 11 December 2014 at 21:35:43 UTC, H. S. Teoh via
> Digitalmars-d-learn wrote:
> >On Thu, Dec 11, 2014 at 08:56:00PM +, Paul via Digitalmars-d-learn
> >wrote:
> >>Is there any merit (or folly!) in storin
On Thursday, 11 December 2014 at 21:35:43 UTC, H. S. Teoh via
Digitalmars-d-learn wrote:
On Thu, Dec 11, 2014 at 08:56:00PM +, Paul via
Digitalmars-d-learn wrote:
Is there any merit (or folly!) in storing a large array, that
frequently needs to be accessed globally, within a class like
so:
On Thu, Dec 11, 2014 at 08:56:00PM +, Paul via Digitalmars-d-learn wrote:
> Is there any merit (or folly!) in storing a large array, that
> frequently needs to be accessed globally, within a class like so:
>
> public class classMap{
>
> public static int[MAPSIZE][MAPSIZE] map;
>
Is there any merit (or folly!) in storing a large array, that
frequently needs to be accessed globally, within a class like so:
public class classMap{
public static int[MAPSIZE][MAPSIZE] map;
}
Or is there a proper 'D' way to do this?
TIA