#region

[coconParticipant]

How about a “#region” feature that it will create some sort of organization of the code base into logical groups (not source code groups). It will be pretty much useful only in the IDE.

Perhaps if there is no point to nag the parser about this, then at least this workaround could be used:

Monkey

#rem region #end

1 2	#rem region #end

If nerobot reads this would decide about this, I just throw the idea.

[codifiesParticipant]

? what for ?

If you need to split a single file into separate regions then its probably about time you, split the code into separate files, considering putting suitable code together in a class, etc….

[coconParticipant]

Not that a file should be humongous, but it leads to a good habit of making clear cuts among the code from the start.

Monkey

Class Level #region Media Field SpriteSheet:Image Method LoadSpriteSheet() End Method DrawSpriteSheet() End #end #region Tileset Field Tiles:Tile[] Method LoadTiles() End #end #region Coordinates Field AnchorPoint:Vector2 Field Size:Vector2 #end #region Checkpoints Field CheckPoints:Vector2[] Method LoadCheckPoints() End #end End ' VS ' Class Level Field SpriteSheet:Image Field AnchorPoint:Vector2 Field CheckPoints:Vector2[] Field Size:Vector2 Field Tiles:Tile[] Method LoadSpriteSheet() End Method DrawSpriteSheet() End Method LoadTiles() End Method LoadCheckPoints() 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 37 38 39 40 41 42 43 44 45 46 47 48

Class Level #region Media Field SpriteSheet:Image Method LoadSpriteSheet() End Method DrawSpriteSheet() End #end   #region Tileset Field Tiles:Tile[] Method LoadTiles() End #end   #region Coordinates Field AnchorPoint:Vector2 Field Size:Vector2 #end   #region Checkpoints Field CheckPoints:Vector2[] Method LoadCheckPoints() End #end End   ' VS '   Class Level Field SpriteSheet:Image Field AnchorPoint:Vector2 Field CheckPoints:Vector2[] Field Size:Vector2 Field Tiles:Tile[]   Method LoadSpriteSheet() End   Method DrawSpriteSheet() End   Method LoadTiles() End   Method LoadCheckPoints() End End

 

Perhaps you might do a counter offer to split the code into sections with standard comments.

Monkey

Class Level ' Tileset _______________ Field Tiles:Tile[] Method LoadTiles() End ' _______________________ ' Coordinates ___________ Field AnchorPoint:Vector2 Field Size:Vector2 ' _______________________ End

1 2 3 4 5 6 7 8 9 10 11 12

Class Level ' Tileset _______________ Field Tiles:Tile[] Method LoadTiles() End ' _______________________   ' Coordinates ___________ Field AnchorPoint:Vector2 Field Size:Vector2 ' _______________________ End

Well, it does the trick in some sort of old-school approach, however the real difference with regions is that you will standardize this principle (of separating the code into sections) by design, rather than doing ASCII art.

[codifiesParticipant]

Its just swapping one ascii soup for another, I just don’t see the point…

[secondgearParticipant]

@codifies #Regions are foldable. I personally find them quite useful, but that’s a matter of taste. They are supported by Jungle and Mollusk.

[nerobotParticipant]

This time Ted2go’s parser is based on mx2cc. When (and if) I will add an additional parsing of local scopes and add foldings.. then we can get this. Folding in editor and in code tree.. dreams

Maybe via comment like this:

‘#region

‘#end

[scurtyParticipant]

Yes, that would be amazing.
+1

[coconParticipant]

nerobot: If Mark doesn’t want to mess the parser further with other additions, this approach ‘#region would work. Let’s see about it in a few months from now.

[Author]

Posts