Re: Compiling Elisp to a native code with a GCC plugin

[Eli Zaretskii]

> From: Lars Magne Ingebrigtsen <address@hidden>
> Date: Fri, 17 Sep 2010 15:17:37 +0200
> 
> Eli Zaretskii <address@hidden> writes:
> 
> > What aspects of buffers and strings you think you might not
> > understand?  Ask here any specific questions you have.
> 
> I mainly wonder how the text in the buffer is really represented.  Is it
> like a string (which is utf8-ish), but with a gap somewhere?

Yes.

> Thanks; that's a helpful node.  However, the node seems to, er, not
> match up to how functions really are written.  The code is full of BEGV,
> PT and CHECK_STRING, which is likely somewhat mysterious to new
> hackers.  At least I was confused.  :-)

BEGV, PT, etc. are covered by the "Buffer Internals" node, except that
they are lowercased there (because they describe the corresponding
struct members to which the upper-cased macros expand).

CHECK_FOO just checks that the Lisp_Object is of type FOO.  This is
useful when you need to be sure you get the arguments of the right
type before you process them.