Description
Cores info files are useless for multi systems cores.
By example there is no reliable way to distinguish system_id, supported_extensions for each system.
Expected behavior
Able to parse per system properties for system id, supported extensions.
Actual behavior
For example in the bluemsx_libretro.info:
Useless entries like:
systemname = "MSX/SVI/ColecoVision/SG-1000"
systemid = "msx"
database = "Microsoft - MSX|Microsoft - MSX2|Coleco - ColecoVision|Sega - SG-1000"
supported_extensions = "rom|ri|mx1|mx2|col|dsk|cas|sg|sc|m3u"
Environment information
- OS: Linux / Flatpak x86_64
Ideas:
For such multi systems cores, we could decide:
- system separator like |
- system multi value separator like ;
- exact same number of entries for properties that matter (systemid and systemname by examples)
- extension sorted by order of declared systems
- system section unknown should be set empty (not skipped)
So for the reported properties, they could become instead:
systemname = "MSX|MSX2|SVI|ColecoVision|SG-1000"
systemid = "msx|msx2|svi|colecovision|sg_1000"
database = "Microsoft - MSX|Microsoft - MSX2|SVI - SVI|Coleco - ColecoVision|Sega - SG-1000"
supported_extensions = "mx1|mx2|dsk;cas|col|sg"
Description
Cores info files are useless for multi systems cores.
By example there is no reliable way to distinguish system_id, supported_extensions for each system.
Expected behavior
Able to parse per system properties for system id, supported extensions.
Actual behavior
For example in the bluemsx_libretro.info:
Useless entries like:
Environment information
Ideas:
For such multi systems cores, we could decide:
So for the reported properties, they could become instead: