The chance that Embarcadero or its current owners implement mode objfpc is also near zero, so I wouldn't bother with a standarization process, since current delphi doesn't support any standard to begin with.
Without standardization, how are we supposed to write Pascal programs? For an experienced Pascal programmer it is obvious, but what about a new programmer? Delphi has a fame, FPC is available to everyone.
FPC should step forward as the authority of Object Pascal language. FPC code is valid Pascal code. More specifically, code written in mode ObjFPC is valid Pascal code.
Personally, I think the objfpc is pointless. I always use mode delphi with FPC and then the issue is moot.
You seem to not care about it just because your code compiles. But if you wrote your program in mode Delphi, it is not a valid Pascal program. Delphi is not a Pascal programming environment, but it may choose to become so. Unless it becomes an FPC-clone, we won't bother with Delphi.
One of Delphi's (and FreePascal's) strengths is that their Pascal dialects are NOT standardized, so the compiler vendors can freely, easily, and quickly change the language as they see fit for their needs. Standardization makes it harder and slower to make changes when needed.
How a language can change so frequently? Object Pascal is just some extensions to standard Pascal. Frameworks may change frequently, this doesn't mean that language will change. To elaborate:
Object Pascal
is not TComponent
Object Pascal
is TObject
Now, how much TObject can change? You can check this draft document to have an idea of how an official standard could be:
http://www.pascal-central.com/OOE-stds.htmlSome compiler implementation details like RTTI, generics, anonymous methods, UTF support etc. may be omitted when preparing a specification. Then, FPC can still be seen as reference platform when comparing implementations.
There may be other compiler vendors who are willing to provide commercial Object Pascal compilers. Such a work will form a foundation for this possibility.