unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Programming starting Lisp
Date: Tue, 12 Aug 2014 10:53:00 -0700 (PDT)	[thread overview]
Message-ID: <cdae6f1c-5398-4e9c-a08e-1b00c5f4efd4@googlegroups.com> (raw)
In-Reply-To: <87ha1hk64w.fsf@debian.uxu>

On Tuesday, August 12, 2014 10:16:39 PM UTC+5:30, Emanuel Berg wrote:
> Rusi writes:

> > I am collecting material on univs starting
> > programming with functional programming:
> > ...
> > I am sure that more places are using Lisp... cant
> > seem to find much.
> > If anyone knows any, in particular non-scheme lisp
> > usage in programming education, please let me know.

> I have said a couple of times that I don't believe in
> paradigms that much. If you tell your students that
> paradigms are models to enhance our understanding, not
> rules what to do, and certainly not descriptions of
> technology (just think of C and Lisp, with which you
> can do anything and everything, in whatever style) - if
> you promise that, ..., no, you don't need to promise
> that, I'll answer anyway:

> Yes, I did Lisp, Erlang and Haskell in a course called
> "Advanced functional programming" at Uppsala
> University, Sweden. But in the CS program there were
> many courses that included functional programming in
> one way or another: SML was the first language I did at
> the university, I did more Erlang on distributed
> systems because of modularity/concurrency, etc. As for
> Lisp in particular, I don't remember that from any
> other course.

> The Lisp we did was Common Lisp. I still have the
> configuration I did to Emacs to do that:

> (setq inferior-lisp-program "/usr/bin/sbcl --noinform")

> sbcl is "Steel Bank Common Lisp", probably some remnant
> of the Lispic wars when there were so much sweet Lisp
> around in different flavors.

> One of the books we read (and the only one I remember)
> was "Land of Lisp", which was very good. I still use
> the style with parenthesis like they did in that book:

> (setq load-path
>       (cl-concatenate 'list load-path
>                       '("~/.emacs.d/emacs-init/"
>                         "~/.emacs.d/emacs-init/w3m/"
>                         "~/.emacs.d/emacs-init/gnus/") ))

> Here are the notes I took on that course with respect
> to CL:

> http://user.it.uu.se/~embe8573/common_lisp/intro.l

> I haven't touched it in all those years (never look
> back), but I passed the course, so it should be mostly
> correct.

Thanks Emanuel for the data
Uppsala occured a couple of times.
However I cant find anything like a syllabus I can point to.

Do you know of one?

In particular if there is something in Swedish and google-translate does
a half-decent job of translating it, that'd be useful


  reply	other threads:[~2014-08-12 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  5:27 Programming starting Lisp Rusi
2014-08-12 16:46 ` Emanuel Berg
2014-08-12 17:53   ` Rusi [this message]
2014-08-12 18:13     ` Emanuel Berg

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=cdae6f1c-5398-4e9c-a08e-1b00c5f4efd4@googlegroups.com \
    --to=rustompmody@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).