@hexaheximal I wonder if it is AI-generated. Appendix A certainly reads like it is, and what other license has a Closing Note? Also this bit is weird:
To the extent permitted by applicable law, This License shall be governed by and interpreted in accordance with the laws of [Jurisdiction], without regard to conflict of law principles.
and section 2.2 seems to be granting a license to use derivative works which violate the license, which seems legally questionable. I’m not a lawyer but I don’t think this has been reviewed by one.
@hexaheximal KLPL does explicitly state:
KLC may have previously been distributed under other licenses, including Creative Commons Attribution-ShareAlike (CC-BY-SA). Those licenses remain fully in effect for copies received under their terms.
but even if it didn’t, neither CC-BY-SA nor AGPLv3 can be revoked so KLPL couldn’t affect the licensing of older versions.
@kemona_halftau true for the first part (I don’t know what to suggest other than not writing code that does that if you want it to be portable), but you can efficiently read and write data in a fixed endianness without writing endianness-specific code or doing unnecessary byte-swaps:
uint16_t load_u16le(const uint16_t *p) {
const uint8_t *b = (uint8_t *) p;
return b[0] | (((uint16_t)b[1]) << 8);
}
compilers know what this is and will optimize it away on little-endian systems