search

liballeg / allegro5

The official Allegro 5 git repository. Pull requests welcome!
https://liballeg.org
Other
1.9k stars 285 forks source link

Fix too many letters #1585

Open MarkOates opened 1 month ago

MarkOates commented 1 month ago

Allegro has inefficient naming conventions. Specifically, typing ALLEGRO_* for every constant is a waste of precious key tying time.

This PR fixes this by replacing all ALLEGRO_ constants with A50_.

Since "ALLEGRO_" takes takes 9 keystrokes (including SHIFT) and "A5O_" takes 6 (including a second re-press of SHIFT), this is a productivity increase of a whopping 33.33% for ALL Allegro users.

pedro-w commented 1 month ago

This is great, and very insightful. Similarly, long words such as 'bitmap' or 'display' could be replaced by 'b' and 'd' respectively for greater efficiency improvement.

Iniquitatis commented 1 month ago

This is great, and very insightful. Similarly, long words such as 'bitmap' or 'display' could be replaced by 'b' and 'd' respectively for greater efficiency improvement.

Don't forget about s for semaphore and m for mutex! 🧐

pmprog commented 1 month ago

Allegro has inefficient naming conventions. Specifically, typing ALLEGRO_* for every constant is a waste of precious key tying time.

This PR fixes this by replacing all ALLEGRO_ constants with A50_.

Since "ALLEGRO_" takes takes 9 keystrokes (including SHIFT) and "A5O_" takes 6 (including a second re-press of SHIFT), this is a productivity increase of a whopping 33.33% for ALL Allegro users.

Seems a really odd question, but you start by mentioned A50, then you go to A5O, with a letter O rather than a zero. Is there much need for either? Surely A5_ would be sufficient enough? I'm in favour :)