News for hackers. Stuff that matters.
Re:Emacs Bytecode Internals (2014) by gravypod on Tuesday December 27, 2016 @08:56AM (#13263127)
"Byte-code compilation is an underdocumented — and in the case of the recent lexical binding updates, undocumented — part of Emacs"

"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."

If I was an emacs fan I'd be weary of this. What happens if the devs are hit by busses? What happens to emacs? No documentation means very little stability.

Re:Emacs Bytecode Internals (2014) by barrkel on Tuesday December 27, 2016 @10:05AM (#13263487)
Bytecode is not a novel idea and I wouldn't expect it to be difficult at all to map the well-known concepts to the particulars of the Emacs implementation.

Documentation of source code is often overrated IMO. Most software isn't difficult to understand if it's at least somewhat well-structured - and when the structure is poor, documentation doesn't help much.

It's usually the application domain that's hard to understand, because that's where global invariants and assumptions live.

(Don't get me wrong: documentation of module boundaries is great, particularly if there are many users of the module, up until you get to APIs, where documentation is essential for a decent experience. Documentation of the innards of software, not so much.)

Re:Emacs Bytecode Internals (2014) by imglorp on Tuesday December 27, 2016 @10:32AM (#13263667)
It was probably a novel application when it was first implemented in emacs 1985-ish (going by the bytecomp.el header comment by JWZ). First editor bytecode? First lisp bytecode? First interpreter bytecode?

O-code predates it by a couple decades for general purpose compilation: https://en.wikipedia.org/wiki/O-code

Re:Emacs Bytecode Internals (2014) by abecedarius on Tuesday December 27, 2016 @05:48PM (#13266908)
Peter Deutsch published a paper on a compact Lisp bytecode in the 70s, http://www.softwarepreservation.org/projects/LISP/interlisp-.... IIRC the Smalltalk-80 bytecode was pretty similar, descended from Smalltalk-76.
Re:Emacs Bytecode Internals (2014) by kazinator on Tuesday December 27, 2016 @08:35PM (#13267796)
The cell counts seem to be off by one in the Appendix examples (REVERSE and SUBST lambdas). I count 35 and 40 conses, respectively. :)
Re:Emacs Bytecode Internals (2014) by barrkel on Tuesday December 27, 2016 @02:23PM (#13265446)
The context of my comment is of course in maintaining the source - the comment I was replying to was concerned with bus numbers.

By the time it was implemented for emacs, many, if not most CS students would have been familiar with p-code as used for UCSD Pascal etc.

Re:Emacs Bytecode Internals (2014) by db48x on Tuesday December 27, 2016 @09:57AM (#13263440)
This page is actually pretty good high-level documentation for the system. Between it and the source code you'll have little difficulty.

Of course, if you have Emacs you'll presumably also have the manuals. Chapter 16 of the Elisp manual seems pretty thorough.

Re:Emacs Bytecode Internals (2014) by wangchow on Tuesday December 27, 2016 @09:10AM (#13263192)
Source code is the ultimate documentation. ;)
Re:Emacs Bytecode Internals (2014) by gnuvince on Tuesday December 27, 2016 @10:14AM (#13263550)
I've started doing literate programming these past two months, and I have to say that I believe this statement less and less.
Re:Emacs Bytecode Internals (2014) by ffggvv on Tuesday December 27, 2016 @09:06AM (#13263175)
That's true for a lot of software. Do you use any SaaS? That's the worse.
Re:Emacs Bytecode Internals (2014) by gravypod on Tuesday December 27, 2016 @09:29AM (#13263290)
The only SaaS I use personally are websites I visit. I host my own ownCloud, file storage, contact backups, and when I move into my new place I'll be setting up my own email server as well.

Edit: If you consider DNS as SaaS then I also use that but I don't need it internally for my network to function so I won't call it a dependancy.

Re:Emacs Bytecode Internals (2014) by espadrine on Tuesday December 27, 2016 @09:24AM (#13263256)
Statistically, death is not the danger. I can't think of a single case where a heavily relied-on project caused major issues from a handful of deaths.

On the other hand, developers losing will… The loss of Gmane, for instance, caused major link breakage for months.

Re:Emacs Bytecode Internals (2014) by GFK_of_xmaspast on Tuesday December 27, 2016 @11:06AM (#13263896)
That was one of the argue points in some of the recent emacs-devel drama about the object dumper.