Ticket #44708

Lua: Prohibited signals

Open Date: 2022-05-29 09:27 Last Update: 2022-07-19 00:39

Reporter:
Owner:
(None)
Type:
Status:
Open
Component:
MileStone:
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
None
File:
None

Details

Coming more acute with #44703:

We need a way to completely stop supporting lua signals that have been deprecated for some time already.

Similar mechanisms will be needed also for the methods, and anything else in the lua API, so consider that in the design.

Ticket History (3/3 Histories)

2022-05-29 09:27 Updated by: cazfi
  • New Ticket "Lua: Prohibited signals" created
2022-06-06 11:13 Updated by: cazfi
Comment

What makes this impossible with our current policies is that the deprecated API can be legitimately in use in a savegame formats that we support. In theory those APIs remain in savegames forever, as they are not updated even when you load the savegame to newer freeciv version and resave. But currently we support even direct loading of such scenario format versions that predate the entire deprecation warnings mechanism.

2022-07-19 00:39 Updated by: ihnatus
Comment

What comes into mind is a mechanism to create user defined events. Define some of them with names of deprecated and removed events and put evoking of them into new signal processors with some necessary framing code, then you can run the legacy code as if the signals still present.

Attachment File List

No attachments

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login