Why Is SQLite Coded in C? (2017)

Re:Why Is SQLite Coded in C? (2017) by 3chelon on Wednesday March 14, 2018 @12:51PM (#16586140)

Well... the declaration you cited resolves down to a pointer to a wide integer. Part of C's simplicity is its small number of keywords, many of which have become way too overloaded as architectures have grown more advanced. The keywords were decided in the 1970s, when address spaces were 16 bits at the most. The ability to create type aliases with `typedef` has added to this apparent complexity, and this has been abused by compiler and OS vendors for decades.

None of it makes the language inherently any more complex, any more than representing machine instructions by long strings of binary makes _them_ any more complex.

[ Parent | on HN ]

Re:Why Is SQLite Coded in C? (2017) by jcelerier on Wednesday March 14, 2018 @01:51PM (#16586770)

> Well... the declaration you cited resolves down to a pointer to a wide integer

With a boatload of associated semantics, quite a bunch bein in practice compiler-dependent (looking at you, MSVC volatile).

And a "protected abstract virtual base pure virtual private destructor" does not mean anything -- or at least any code that compiles.

[ Parent | on HN ]

Re:Why Is SQLite Coded in C? (2017) by saagarjha on Wednesday March 14, 2018 @04:08PM (#16587848)

> With a boatload of associated semantics, quite a bunch bein in practice compiler-dependent (looking at you, MSVC volatile).

Which is not part of C. Your argument that "C is complicated" doesn't work if you cite an egregious misuse of nonstandard extensions.

[ Parent | on HN ]

Re:Why Is SQLite Coded in C? (2017) by 3chelon on Monday March 19, 2018 @03:12PM (#16622039)

Forgive my ignorance here, I'm genuinely intrigued: what's so special about MSVC's volatile as opposed to the regular volatile keyword?

[ Parent | on HN ]