From: Raghav Gururajan <raghavgururajan@disroot.org>
To: rekado@elephly.net, mail@ambrevar.xyz, jgibbons2357@gmail.com,
vas@oneofus.la, me@tobias.gr, znavko@disroot.org, jsoo1@asu.edu
Cc: help-guix@gnu.org
Subject: Re: Help with Learning Programming and LISP
Date: Wed, 11 Sep 2019 21:16:39 -0400 [thread overview]
Message-ID: <05840a988fb0592a67f8372650aba5cdc81b499e.camel@disroot.org> (raw)
In-Reply-To: <874l1l9qnd.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
Hello Everyone!
Thank you all for your suggesstions.
After careful review, I have chose following books to read:
PROGRAMMING CONCEPTS:
1) Structure and Interpretation of Computer Programs
2) How to Design Programs
COMMON LISP:
1) ANSI Common LISP
EMACS LISP:
1) An Introduction to Programming in Emacs LISP
SCHEME:
1) The Scheme Programming Language
:-)
I have a doubt though, do I have to learn dialects of LISP in a
particular order?
Regards,
RG.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-12 1:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 16:18 Help with Learning Programming and LISP Raghav Gururajan
2019-09-09 16:38 ` John Soo
2019-09-09 17:04 ` Raghav Gururajan
2019-09-09 17:20 ` Jesse Gibbons
2019-09-09 16:50 ` Tobias Geerinckx-Rice
2019-09-09 16:53 ` Tobias Geerinckx-Rice
2019-09-09 17:05 ` John Soo
2019-09-09 17:04 ` Raghav Gururajan
2019-09-09 17:20 ` Pierre Neidhardt
2019-09-09 17:18 ` Vladimir Sedach
2019-09-09 20:11 ` Ricardo Wurmus
2019-09-12 1:16 ` Raghav Gururajan [this message]
2019-09-12 6:34 ` Konrad Hinsen
[not found] <mailman.370.1568090751.2189.help-guix@gnu.org>
2019-09-10 20:31 ` Zelphir Kaltstahl
2019-09-11 20:53 ` Viet Le
2019-09-11 21:24 ` Zelphir Kaltstahl
2019-09-11 22:15 ` Viet Le
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05840a988fb0592a67f8372650aba5cdc81b499e.camel@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=help-guix@gnu.org \
--cc=jgibbons2357@gmail.com \
--cc=jsoo1@asu.edu \
--cc=mail@ambrevar.xyz \
--cc=me@tobias.gr \
--cc=rekado@elephly.net \
--cc=vas@oneofus.la \
--cc=znavko@disroot.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.