Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!sdd.hp.com!spool.mu.edu!cs.umn.edu!ariel.unm.edu!nmsu!opus!ted
From: ted@nmsu.edu (Ted Dunning)
Newsgroups: comp.lang.scheme
Subject: Re: Why memq vs memv vs member, etc.?
Message-ID: <TED.91May10214634@kythera.nmsu.edu>
Date: 11 May 91 03:46:34 GMT
References: <1991May10.230057.15591@Think.COM>
Sender: news@NMSU.Edu
Organization: Computing Research Lab
Lines: 17
In-reply-to: barmar@think.com's message of 10 May 91 23:00:57 GMT


In article <1991May10.230057.15591@Think.COM> barmar@think.com (Barry Margolin) writes:

   Why not (member <obj> <list> eq?) instead of (memq <obj> <list>)?


well, while we are at it, why have member at all?

why not just


  (some (lambda(x) (eq? <obj> x)) <list>)

--

if feeling bad is a justification for not living, 
    then living is a justification for feeling good.