>
> Peter N Lewis wrote:
> > If FPC implements "const var", then this issue will die (except for
> > minior compatibility issues with the EOLed MW Pascal).
>
> I must admit, I don't like the const var syntax. Reasons:
> - it's not necessary to determine per parameter the way how "const"
> parameters are passed, it's enough to tell the compiler: let this
> function/(call) look like it was generated by a MW compiler
> - const var influences only the code generation and makes neither a
> syntactic nor a semantic difference visible to the user so it should
> exposed as little as possible to the user
> - adding the const var to interface units is error prone
> - it might be possible that some has a MW compiled library with an
> interface unit: adding the const var is error prone, adding an ifdef'ed
> {$calling mwpascal} is easy.
>
> Did I overlook something?

I also prefer the global solution (directive) over yet another language
extension.
_______________________________________________
MacPascal mailing list
MacPascal@list...
http://lists.sonic.net/mailman/listinfo/macpascal