From: Drew Adams <drew.adams@oracle.com>
To: Jean-Christophe Helary <brandelune@gmail.com>,
help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: RE: concat vs format
Date: Sat, 8 Dec 2018 20:09:11 -0800 (PST) [thread overview]
Message-ID: <a91ff9fb-a52c-4a2f-8b57-5d108f502e68@default> (raw)
In-Reply-To: <6038B67F-98A7-42B9-8486-97DB99D63033@gmail.com>
> Is there a difference between:
> (concat firstPartofURL secondPartofURL) and
> (format "%s%s" firstPartofURL secondPartofURL)?
If both args are strings then no; the result
is the same. But the functions are very
different - they take different args and,
aside from some cases like this one where
the result is the same for some args, their
uses/purposes are different.
next prev parent reply other threads:[~2018-12-09 4:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 3:50 concat vs format Jean-Christophe Helary
2018-12-09 4:09 ` Drew Adams [this message]
2018-12-09 10:02 ` Jean-Christophe Helary
2018-12-09 11:30 ` Stefan Huchler
2018-12-09 13:42 ` Jean-Christophe Helary
2018-12-09 14:15 ` Stefan Monnier
2018-12-09 14:55 ` Jean-Christophe Helary
2018-12-09 14:57 ` Stephen Berman
2018-12-09 15:44 ` Jean-Christophe Helary
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=a91ff9fb-a52c-4a2f-8b57-5d108f502e68@default \
--to=drew.adams@oracle.com \
--cc=brandelune@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).