help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lisp style question


From: Pascal J. Bourguignon
Subject: Re: lisp style question
Date: Sun, 05 Dec 2010 19:40:51 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Katalin Sinkov <lispstylist@gmail.com> writes:

> On Dec 4, 4:05 pm, Don Geddis <d...@geddis.org> wrote:
>> Katalin Sinkov <lispstyl...@gmail.com> wrote on Thu, 2 Dec 2010 :
>>
>> > what is "setf" and how to write it in terms of the elementary
>> > functions, car/cdr/cons/quote/cond/atom/eq ?
>>
>> Unlike your subject line, this is no longer a "lisp style" question.
>
>> That's fine, but before asking "style" questions, you ought to learn
>> some lisp.  Get an introductory tutorial (there are good free ones
>> online!), try some examples.  After you learn a bit of lisp, and can
>> write simple programs, perhaps then you can come back with some style
>> questions.
>
> OK, I read the papers by McCarthy and the evaluator.
>
>> You just don't know lisp.
>
> Do you know lisp ? Do you even know how to fork off another thread if
> that is your issue with the heading ? Also, style cannot be decoupled
> from skill of language. Even if you learnt all the C, you could not
> write a C++ style virtual class in it unless you had the skill. The
> most you would be able to achieve would be methods with function
> pointers.
>
>> Oh, and by the way: the functions your listed are not "the elementary
>> functions" (lisp has lots of functions, and there is no unique
>> elementary subset); nor can SETF be written in terms of the ones you
>> listed.
>
> But you have one set provided to you on silver plate to use. Must I
> provide you with all of them before you will activate your neuron and
> lift your finger to explain how setf is implemented ?

You don't seem to know how to fork a new thread either.  I'm somewhat
reluctant to answer to this setf question, in a thread that seems to
have turned to a personal flamewar.


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]