Re: master b72f885: Make dlet work like let, not let*

[Jean Louis]

* Tassilo Horn <tsdh@gnu.org> [2021-09-21 11:52]:
> > As a side note, the advise for variables to be first `defvar-ed' if
> > they are to be used in `let*' is not practical. It increases work, it
> > does not lessen the work.
> 
> The advice is to defvar variables which should be dynamically bound, and
> to have few of them because dynamic scope is very hard to debug.  So the
> work saved at coding time might be invested when debugging
> later. ;-)

I understand the approach. On my side I look at it practically. I had
no problems with the implementation.

> > You know when you start creating `let*' variables you don't want to
> > think much, just do it. Now I am supposed to make 50-100 `defvar-ed'
> > variables.
> 
> Well, it seems not to match your design.  If I would try to build a
> templating system I'd try to have just one defvar-ed wcr::variables and
> access that when replacing the template placeholders rather than having
> to dlet each and every thing inside vcr::variables.

I understand idea, though I think with uncertainty, it would bring the
unwanted limitations.

With certainty I know that such change would give more problems then
it is worth, not less.

Once programmed it worked for months, and I have not touched it until
today. 

The RCD Template system it will interpolate any passed variables in
hash first, if any is there, otherwise global variables, including any
Emacs Lisp code. It does not expect by rule variables to be passed.



Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/