Re: auctex 11.83 fills paragraph incorrectly

Re: auctex 11.83 fills paragraph incorrectly

[David Kastrup]

Ralf Angeli <angeli@caeruleus.net> writes:

> * David Kastrup (2006-06-29) writes:
>
>> Given the latest TeX-doc reports, we maybe should consider pushing out
>> 11.84 soon.  That could clear the ground for some of your pending
>> larger changes.
>
> If Emacs Lisp just supported pass-by-reference, then I could get
> easily get rid of some duplicated font locking code.  Oh well, I'll
> find another way.

Emacs Lisp supports quite a number of ways of passing by reference.
Cons cells are passed as pointers, arrays are passed by reference, and
symbols can easily be passed by reference, too.  Quote them at the
point of call, and use `set' instead of `setq' on them.

What are you trying to achieve?

Followup to emacs-devel.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: [Bug-AUCTeX] auctex 11.83 fills paragraph incorrectly

[Ralf Angeli]

* David Kastrup (2006-06-29) writes:

> Ralf Angeli <angeli@caeruleus.net> writes:
>
>> If Emacs Lisp just supported pass-by-reference, then I could get
>> easily get rid of some duplicated font locking code.  Oh well, I'll
>> find another way.
>
> Emacs Lisp supports quite a number of ways of passing by reference.
> Cons cells are passed as pointers, arrays are passed by reference, and
> symbols can easily be passed by reference, too.  Quote them at the
> point of call, and use `set' instead of `setq' on them.
>
> What are you trying to achieve?

There is some duplicated code in the new font locking code I'd like to
move into its own function.  The code manipulates at least one
variable local to the function it is currently used in.  Instead of
defining a global variable for it, it would be nice to pass a
reference to the new function containing the now duplicated code.  The
new function would then manipulate the value of the variable in the
original function.  It's not a big deal, I'll probably just define the
variable globally.

-- 
Ralf