@ PascalDragon
Thank you for your concern.
If you want to avoid code being committed that does not follow your intended formatting you might be better helped with a commit hook in your version control system that runs a source code formatter and complains if something had to be adjusted or something like that...
Could you suggest to me, politely, some guidance where to delve into that topic? I have little practice in the area you have indicated.
Here is a summary description of where my question originates. (I apologize in advance if it becomes unclear.)
I was commissioned to convert source codes (codes are closed), written in an internal corporate language, to a modern language. At the same time, a change in hardware architecture will be made.
I chose to use FPC as the target language.
I have no problem converting, and where necessary to correct and optimize, sources written with the old language to the FPC.
The problem is that the codes must be validated on the old architecture used previously for which the codes were written. So after I translate them into FPC I have to convert them back into the old language. Fortunately, a converter had already been written from a Pascal dialect to the old corporate language. Pascal's dialect uses a syntax of the type described in my previous post.
I had asked about the existence of custom directives to the FPC compiler, to avoid having to write an additional parser.
The use of tongue-in-cheek phrases to the comments was due to the fact that I would have preferred that the validation phase had not been necessary.
Otto.