Inline::C works during module load time, so "just-ahead-of-time" is a better description of it than "just-in-time". I don't think "JAOT" is a well-known enough acronym, so it's worth spelling it out. --- HACKING | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/HACKING b/HACKING index 74a3096f..fbcfb552 100644 --- a/HACKING +++ b/HACKING @@ -40,8 +40,8 @@ the shiny new. Avoid relying on compiled modules too much. Even if it is Free, compiled code makes packages more expensive to audit, build, distribute and verify. public-inbox itself will only be implemented -in scripting languages (currently Perl 5) and optional JIT-compiled C -(via Inline::C) +in scripting languages (currently Perl 5) and optional +Just-Ahead-of-Time-compiled C (via Inline::C) Do not recurse on user-supplied data. Neither Perl or C handle deep recursion gracefully. See lib/PublicInbox/SearchThread.pm -- unsubscribe: one-click, see List-Unsubscribe header archive: https://public-inbox.org/meta/
