[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using "Emacs Configure" **and** modifying .emacs

From: tomas
Subject: Re: Using "Emacs Configure" **and** modifying .emacs
Date: Sat, 12 Aug 2017 10:02:05 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

Hash: SHA1

On Sat, Aug 12, 2017 at 09:43:23AM +0200, Emanuel Berg wrote:
> tomas wrote:
> > Some dont want a validation to explode deep
> > whithin the guts of some module loaded by
> > another module, where the user has no clue
> > about what the heck is going on, but next to
> > the place where a variable is being set to
> > a value it's not supposed to have.
> >
> > Sometimes I can sympathize with that :-)
> One could also put validation at the beginning
> of the functions that use the value, where it
> (the function) checks its own parameters rather
> than some global loose-cannon variable!

This is waht I meant by "guts": imagine Tramp, which
uses some access method deep in another module, which
then, for the first time, needs the variable. That
happens dynamically, at the moment you try to access
a file dependent on this method, long (perhaps weeks)
after you set the variable. Not very debugging-friendly.

Similarly (just another aspect of the same thing), this
can do away with that pesky "eval-after-load" you'd
need with the setq approach.

> Which is also a much better design this
> specific issue aside...

Hm. I get your point, but I get the opposite point,
too. "Better design" isn't always an absolute.

- -- tomás
Version: GnuPG v1.4.12 (GNU/Linux)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]