Mirror of github.com/cira0100/Eglantine-public nx2, a fork of Djihads80/Eglantine. https://git.cirakg.xyz/eglantine-cirakg/atom?h=nx2 2019-10-13T17:46:10+00:00 2019-10-13T17:46:10+00:00 Zach Hilman zachhilman@gmail.com 2019-07-05T22:49:52+00:00 urn:sha1:cd8c6a4afd05d9adc142a85847c0ba9e94fb0f28 2019-09-22T07:47:25+00:00 David Marcec dmarcecguzman@gmail.com 2019-09-22T07:47:25+00:00 urn:sha1:f35665aa288b46d53403dd92621ec150e18b597a This reverts commit 66d80be727ca3254cec21b32d868155b0fa296d1, reversing changes made to 43decd168129895c8ea82fdb60dfbea95386a1fd. 2019-09-21T23:21:22+00:00 Zach Hilman zachhilman@gmail.com 2019-07-05T22:49:52+00:00 urn:sha1:896045aa4ffb563d9d37dc382fe5e8a4f4ed2c56 2018-09-11T08:25:33+00:00 Lioncash mathew1800@gmail.com 2018-09-11T08:15:36+00:00 urn:sha1:642d916bdb203e89700c70855956f627a2a9ad71 This places the font data within cpp files, which mitigates the possibility of the font data being duplicated within the binary if it's referred to in more than one translation unit in the future. It also stores the data within a std::array, which is more flexible when it comes to operating with the standard library. Furthermore, it makes the data arrays const. This is what we want, as it allows the compiler to store the data within the read-only segment. As it is, having several large sections of mutable data like this just leaves spots in memory that we can accidentally write to (via accidental overruns, what have you) and actually have it work. This ensures the font data remains the same no matter what.