unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: fatiparty--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Elisp function that performs numeric computations
Date: Fri, 21 Jan 2022 13:25:55 +0100 (CET)	[thread overview]
Message-ID: <MtwaQEg--3-2@tutanota.com> (raw)
In-Reply-To: <87sfthtigj.fsf@zoho.eu>

Jan 21, 2022, 23:51 by help-gnu-emacs@gnu.org:

> fatiparty--- via Users list for the GNU Emacs text editor wrote:
>
>> (defun test (dcur dmax drpt)
>>
>
> All programming: Name the function something that etc etc.
>
> Lisp: We don't name formal parameters the assembly language or
> C style ... give them short, but if possible complete names
> that are easy to read and write. When in doubt, give them
> a complete name that communicates what its purpose or
> intended use.
>
>> "Compute brace depth used for brace colouring."
>>
>
> Doc string should have the formal parameter's names in BOLD in
> the order they come in the the function definition ...
>
>> (interactive)
>>
>
> Assign the formal parameters with argument values
>
> (interactive "ndepth: \nntop: \nnrepeat: ")
>  ^ eval me
>
> Use English in the prompt string, if the words feel to long
> see if they can be shortened in a natural way (here, e.g. dep,
> top, and rep) - the reason one avoids "max" is it also appears
> in as the function `max' ...
>
>> (let ( (n dcur) )
>>  (message "dcur <= dmax | Typeface: %d" n)
>> n)
>>
>
> If there is no computation, renaming it ... why do you
> do that?
>

I did that because I use n an the output (either it is dcur [current depth] or it is from the
latter computation).

But as you say, I could just do

(if (<= dcur dmax)      dcur

(let* ( (j drpt) ...



> You use it like this:
>
> (let*((side 2)
>  (square (expt side 2) )) ...
>  ;; use square here
>  )
>
> -- 
> underground experts united
> https://dataswamp.org/~incal
>




  reply	other threads:[~2022-01-21 12:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19  7:20 Elisp function that performs numeric computations fatiparty--- via Users list for the GNU Emacs text editor
     [not found] ` <MtlCLWs--3-2@tutanota.com-MtlItBn----2>
2022-01-19  9:03   ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-19 10:14     ` tomas
2022-01-19 11:29       ` Marcin Borkowski
2022-01-19 22:52         ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-20 22:53           ` Sergey Organov
2022-01-21  8:23             ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-21 11:39               ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-21 13:03                 ` Sergey Organov
2022-01-21 15:32                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-21 17:13                     ` Sergey Organov
2022-01-21  9:04             ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-21 11:51               ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-21 12:25                 ` fatiparty--- via Users list for the GNU Emacs text editor [this message]
     [not found]         ` <MtoXj5p--3-2@tutanota.com-MtoXrZH----2>
2022-01-20 18:17           ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-19 10:24     ` Manuel Giraud
2022-01-19 17:31     ` Eduardo Ochs
2022-01-19 15:31 ` Michael Heerdegen
2022-01-19 18:41   ` H. Dieter Wilhelm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MtwaQEg--3-2@tutanota.com \
    --to=help-gnu-emacs@gnu.org \
    --cc=fatiparty@tutanota.com \
    --cc=moasenwood@zoho.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).