From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: macros vs HOFs (was: O'Caml) Date: 11 Sep 2002 22:59:55 +0000 Organization: Naggum Software, Oslo, Norway Lines: 21 Message-ID: <3240773995474691@naggum.no> References: <3D7CB8DF.8050108@pontos.net> <3240690993463545@naggum.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: maud.ifi.uio.no 1031785195 8864 129.240.64.16 (11 Sep 2002 22:59:55 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 11 Sep 2002 22:59:55 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:40369 * Gareth McCaughan | I should perhaps add that making int/int *not* truncate is in the plans for | Python's future. You can imagine the backward-compatibility nightmares. Will there be a new infix operator for the real division? I have seen // used for this purpose, but some jerk had to use it up for comments. (Even in C++, ;; could be used for comments.) | Oh, and can I put in a plea for not using "strong" to mean "static" in this | context? C is statically typed but not strongly typed. CL is strongly typed | but not statically typed. And, in the interests of completeness: Perl is | neither strongly typed nor statically typed; Pascal is both strongly and | statically typed. This is worthwhile clarification. Thanks. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.