What I propose is one set of rules for a specific language that is accessible to any Programmer of said language.
Providing they're working on a specific project or sub-genre? This concept is no different than assigning a Moderator to a forum.
And equally ineffective. What would be the incentive for an expert programmer to look through potentially thousands of lines of other peoples code, to ensure that it complies to a set of arbitrary rules? If they do use it and certify their source code, other Programmers who use certified B3DFS Source Code are empowered to read and expand that source code.
How is that different from the current situation? You can do that equally well without standardization, particularly since Blitz3D was not designed in a standards-friendly way, and the IDE goes out of it's way to make standardization more difficult. Never mind that standardization is impractical in a procedural language with limited scope (like Blitz3D) as it'll lead to all sorts of symbol collisions. -> blackbox method <-
Unfortunately due to lack of language features, you can't really black box Blitz3D programs. Even BlitzMAX is (due to the lack of working access modifiers) somewhat difficult to blackbox, as you cannot properly control the exposed Interface. My key point is that the Programmer has the OPTION to use B3DFS or not.
I don't get it tho'. What exactly are you proposing here? How is it going to work with a primitive language like Blitz3D? What is the point? It's not like Blitz3D allows you the flexibility to use it in more ways than one. Blitz3D already has it's own standardization (enforced by the language - like all types must be stored in lists etc.), trying to diverge from that seems rather counter productive and frankly rather pointless.