Timeline for Are any scripting languages designed to be reloaded at runtime?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2013 at 20:09 | comment | added | Richard Copperwaite | You're right, persistence is the real issue here, and this has highlighted one of the major problems with TinyPy - it has a complete lack of any runtime type information, making deserialization extremely difficult. Perhaps now would be the time to switch back to full Python, and use a library like Pickle to marshal my state between script refreshes, and also between game sessions. | |
| Feb 2, 2013 at 18:37 | vote | accept | Richard Copperwaite | ||
| Jan 31, 2013 at 22:53 | comment | added | Nicol Bolas | Note that there is a caveat here: to do this, your old scripts will have to write their appropriate data in a format that the new scripts can read and understand. If your new scripts change radically, that may not be possible. Obviously for a shipping game, you don't want to wreck everyone's save games for a patch, so you would be careful with how you change your AI or you implement versioned loading. But during development, you want to be agile, not burdened with having to load outdated versions of data. So there can be a downside to this. | |
| Jan 31, 2013 at 21:55 | history | answered | Kevin Reid | CC BY-SA 3.0 |