Posted: Wed Apr 10, 2002 6:01 pm
Restored from previous forum. Originally posted by DarkUni.
I've written Fred about this, but I'm curious about the group's thoughts on it.
When writing in PB, you are required to have PROCEDURES created in the code BEFORE its ever referenced - this requires a form of sequentiality that really bugs me.
Typically, when I code, I use this format:
The main loop is typically where I compile my collection of Function/Procedure calls. Functions/Procedures are typically added constantly throughout development, so it makes it easy to PAGE DOWN to the end, add a new Procedure, link it in the Main Loop.
In PB, however, Procedures are REQUIRED to come before ANY references to them (i.e. the Main Loop).
Now I'm not saying my way is the RIGHT way; however, it seems unnecessarily restrictive to REQUIRE the typically 'detattached' Procedure code to be present before its references to it.
I've looked at a lot of PB code, and it seems as is Procedures (by and large) and not very popular here (life's blood for me in Blitz - Everything is a function; and it drastically increases performance in game development - I learned the hard way). Perhaps this is the reason no one else speaks of this or it doesn't bother too many people because they just don't use them as a rule.
Anyway, that's my outlook. I was hoping this restriction would go away with 3.0, but its still there. It makes me porting games from Blitz that much more challenging - but I would like to.
Anyone in agreement, or am I just a dork?
Note: I'm not talking about referencing Procedures that DON'T EXIST yet - I'm talking about a procedure that is LOWER in the code listing than the reference:
In this sample, procedure 1 can be called from the Main Loop. Procedure 2 cannot be - even though they both exist and are functional.
Thanks guys!
Shane R. Monroe, Dark Unicorn Productions
Pure Basic Basement
http://pb.darkunicornproductions.com
I've written Fred about this, but I'm curious about the group's thoughts on it.
When writing in PB, you are required to have PROCEDURES created in the code BEFORE its ever referenced - this requires a form of sequentiality that really bugs me.
Typically, when I code, I use this format:
The main loop is typically where I compile my collection of Function/Procedure calls. Functions/Procedures are typically added constantly throughout development, so it makes it easy to PAGE DOWN to the end, add a new Procedure, link it in the Main Loop.
In PB, however, Procedures are REQUIRED to come before ANY references to them (i.e. the Main Loop).
Now I'm not saying my way is the RIGHT way; however, it seems unnecessarily restrictive to REQUIRE the typically 'detattached' Procedure code to be present before its references to it.
I've looked at a lot of PB code, and it seems as is Procedures (by and large) and not very popular here (life's blood for me in Blitz - Everything is a function; and it drastically increases performance in game development - I learned the hard way). Perhaps this is the reason no one else speaks of this or it doesn't bother too many people because they just don't use them as a rule.
Anyway, that's my outlook. I was hoping this restriction would go away with 3.0, but its still there. It makes me porting games from Blitz that much more challenging - but I would like to.
Anyone in agreement, or am I just a dork?
Note: I'm not talking about referencing Procedures that DON'T EXIST yet - I'm talking about a procedure that is LOWER in the code listing than the reference:
In this sample, procedure 1 can be called from the Main Loop. Procedure 2 cannot be - even though they both exist and are functional.
Thanks guys!
Shane R. Monroe, Dark Unicorn Productions
Pure Basic Basement
http://pb.darkunicornproductions.com
