2 ms·
I made no mention of Lua. The context is C and assembly programmers as an audience. But let's consider Lua. Most of the Lua pogrammers I know also know C. H
by __b__ 10y ago
I made no mention of Lua. The context is C and assembly programmers as an audience.
But let's consider Lua. Most of the Lua pogrammers I know also know C. How do they handle the so-called "impedence mismatches"? (Should this be plural? What else besides 1-based arrays?)
As far as I know Lua's target audience is, at least in part, C programmers. That's why it's made to be easy to embed in a C program.
- dalke 10y agoJoshTriplett's comment was a response to "why would they not use lua?" The points were all made relative to "C and assembly programmers" using Python vs. the same using Lua. You can't simply pull a few words out of the comment and assume it means there is no mismatch what C programmers expect and what Python offers. It doesn't mean that and wasn't meant to mean that. You wrote "Lua's target audience is, at least in part, C programmers". That is also true of CPython. Bear in mind that these facts aren't that relevant. This code is not mean for the wider class of "C programmers". The relevant bit is "the target audience writes assembly and C". This is far different than "the target audience is assembly and C programmers", which appears to be what you think it says. Instead, the target audience is the narrower class of people writing EFI binaries and working with the EFI protocol. As JoshTriplett further clarified, the "existing development tools in that area already support Python", but apparently not in Lua.
- __b__ 10y agoTo sum up, the target audience was EFI developers who would prefer to write Python than write assembly, C or Lua. No problem. I get it.
- metalliqaz 10y agoFound the Lua developer!