[Gerry QuinnParticipant]

This was easy enough in Original Monkey, and I would imagine that a variation could be used in Monkey 2.  The trick was that if you already made a templated 1D array copy, you can then use it in your 2D one, and so on.  OFC you still need to make separate ones for as many dimensions as you think you’ll need, but not much coding is involved.  Here is the Monkey X version:

Class for generic functions

Monkey

' Class for generic functions Class Generic< T > ' Return a copy of the passed 1D array (will not 'deep copy' objects, just copies references) Function CopyArray:T[]( orig:T[] ) Local len:Int = orig.Length() Local arr:T[] = New T[ len ] For Local i:Int = 0 Until len arr[ i ] = orig[ i ] Next Return arr End ' Return a copy of the passed 2D array (will not 'deep copy' objects, just copies references) Function CopyArray:T[][]( orig:T[][] ) Local len:Int = orig.Length() Local arr:T[][] = New T[ len ][] For Local i:Int = 0 Until len arr[ i ] = CopyArray( orig[ i ] ) Next Return arr End ' Return a copy of the passed 3D array (will not 'deep copy' objects, just copies references) Function CopyArray:T[][][]( orig:T[][][] ) Local len:Int = orig.Length() Local arr:T[][][] = New T[ len ][][] For Local i:Int = 0 Until len arr[ i ] = CopyArray( orig[ i ] ) Next Return arr End End

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

' Class for generic functions Class Generic< T >   ' Return a copy of the passed 1D array (will not 'deep copy' objects, just copies references) Function CopyArray:T[]( orig:T[] ) Local len:Int = orig.Length() Local arr:T[] = New T[ len ] For Local i:Int = 0 Until len arr[ i ] = orig[ i ] Next Return arr End ' Return a copy of the passed 2D array (will not 'deep copy' objects, just copies references) Function CopyArray:T[][]( orig:T[][] ) Local len:Int = orig.Length() Local arr:T[][] = New T[ len ][] For Local i:Int = 0 Until len arr[ i ] = CopyArray( orig[ i ] ) Next Return arr End ' Return a copy of the passed 3D array (will not 'deep copy' objects, just copies references) Function CopyArray:T[][][]( orig:T[][][] ) Local len:Int = orig.Length() Local arr:T[][][] = New T[ len ][][] For Local i:Int = 0 Until len arr[ i ] = CopyArray( orig[ i ] ) Next Return arr End End

[Gerry QuinnParticipant]

Activity on the original Monkey forum seems to be dropping fast.  I assume part of it is that active posters are coming here instead.

I don’t like fragmentation

Activity – even if it’s not relevant to a user’s particular issue – helps keep up motivation and confidence.

[Gerry QuinnParticipant]

I’ve done something like this in the past with spritesheet images – but I just used a point to define the sprite, knowing what the basic size of the image and its sprites is.

I think a sprite atlas as such should probably be a real atlas, with arbitrary packed images.

This design might suit some users, especially for a tile-based game – but it is a very specific approach, and might be best done ad hoc for such a game.

[Gerry QuinnParticipant]

This isn’t Monkey 2 specific, but like Mark and jondecker, I would just try to develop my game in an OO fashion, then when it’s done, refactor out the particular system into a module for my next game.

[Gerry QuinnParticipant]

As several people have noticed, there’s no difference in C++ apart from the default access specifier, and apparently a template thing I didn’t know about.  When I coded in C++ I never used the struct keyword at all, on the basis that it was redundant – a hangover in the interests of C compatibility.  (This was long before C# made structs fashionable, in an attempt to pull back from the restrictions of Java.)

However, I think that in the interests of nice target code, they should probably use whichever was originally set.  And if one is to be used always, I think it should be class, even if that means a bunch of redundant ‘public’ keywords too.

[Author]

Posts