TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Emacs Bytecode Internals (2014)

120 pointsby nochover 8 years ago

4 comments

_ph_over 8 years ago
Nice article, but I was surprised to read that array accesses are not range checked for speed concerns. The emacs byte code interpreter is not known to be a very fast one, I doubt that the range checks would make a significant difference in run time. If anything, byte codes should bring high levels of safety.
评论 #13263882 未加载
评论 #13263412 未加载
评论 #13264787 未加载
评论 #13267087 未加载
khananover 8 years ago
Article might need a 2014-tag.
评论 #13264085 未加载
mmrezaieover 8 years ago
&quot;People do not write byte-code; that job is left to the byte compiler. But we provide a disassembler to satisfy a cat-like curiosity.&quot;<p>How dare they! I will use that disassembler with my dog like curiosity.
评论 #13263329 未加载
gravypodover 8 years ago
&quot;Byte-code compilation is an underdocumented — and in the case of the recent lexical binding updates, undocumented — part of Emacs&quot;<p>&quot;People do not write byte-code; that job is left to the byte compiler. But we provide a disassembler to satisfy a cat-like curiosity.&quot;<p>If I was an emacs fan I&#x27;d be weary of this. What happens if the devs are hit by busses? What happens to emacs? No documentation means very little stability.
评论 #13263487 未加载
评论 #13263440 未加载
评论 #13263192 未加载
评论 #13263175 未加载
评论 #13263896 未加载