Skip to content
This repository was archived by the owner on Jan 31, 2020. It is now read-only.
This repository was archived by the owner on Jan 31, 2020. It is now read-only.

File forward compatibility #50

@dhardy

Description

@dhardy

This needs rethinking. Currently each change to the file format gets a new version number, and the program refuses to deal with anything from the future, meaning that any small change breaks backward compatibility.

Suggestion 1: include two numbers in the file: current version and oldest (potentially) compatible version. From previous experience this approach is a bit inexact and error-prone.

Suggestion 2: use only a "major" version number which doesn't usually change and add "features".

Suggestion 3: use only a "major" version number and just let the program "panic" when it finds something strange.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions