User Tools

Site Tools


midres_library:isomorphism:rules
Translations of this page:


THE ABSTRACTION THAT IS NOT THERE

What I REALLY want to do is avoid introducing an abstraction layer (even mine!) on 8-bit machines, because they don't have the computing power and resources to handle it; at the same time, I would like to avoid writing a program for each platform, also because I would be forced to test all versions.

Let's say I'm aiming for a “WORA without framework”.

To do this, you need to set rules and stakes.

IT IS NOT POSSIBLE:

  • build a framework (it violates the “no framework” assumption);
  • write specific code for a machine (it violates the “WORA”);
  • adopt other dev-kits (it violates the “WORA” and the “without framework”);
  • convert the data to format at the time of compilation (it violates “WORA”)1);

IT IS POSSIBLE:

  • exploit the analogies (isomorphisms) between computers;
  • generalize the code (writing functions);
  • optimize this code;
  • collect it in a library (if the linker supports it);
  • optimize the binary (with scripts);
  • outsource data management (with scripts);
  • reduce data occupation, modifying its organization;

This is the MIDRES project (and library).

Move to page THE ADVANTAGES OF ISOMORPHISM.

1)
currently, I'm not sure that this rule is required