Open tueda opened 1 week ago
A run-time message seems good, as you say users may just use the distributed binaries rather than compiling themselves. This would be the first "--" option, is it more consistent to use a single "-" like -pipe
? I have no strong opinion there.
I was considering the convention for long-name options in GNU tools (other than GCC), but this makes sense (-pipe
already exists). I'll switch it to -ignore-deprecation
.
If you have a better name than -ignore-deprecation
/FORM_IGNORE_DEPRECATION
, then let me know.
This is an implementation of deprecation messages like those in https://github.com/vermaseren/form/issues/475#issuecomment-2146949223 but at runtime startup rather than at build time, for Windows, 32bit builds and ParFORM.
End users may not build binaries themselves. 32-bit binaries and ParFORM are distributed by various distributors. We can distribute native Windows binaries if https://github.com/vermaseren/form/pull/511 is merged and
Delete Windows binaries
indeploy.yml
is removed. This patch will cause these end users to see annoying deprecation warnings.The deprecation warning looks like, for example, for ParFORM:
This warning can be suppressed by the (undocumented)
--ignore-deprecation
option or the environment variableFORM_IGNORE_DEPRECATION=1
.TODO: we need 3 separate issues for users to leave comments regarding the deprecation.