Re: What are the domains that lisp doesn't fit int?



Frank Buss <fb@xxxxxxxxxxxxx> writes:

Duane Rettig wrote:

Huh? Syntax? There are two ways you can look at this: Either Common
Lisp defines no syntax for anything, and the issue becomes the "when
did you stop beating your wife?" question, or else it defines the
syntax for everything, to wit: "(<operator> <argument> ...)".

Maybe "syntax" was the wrong word for Lisp. What I mean is that in C it is
defined, that an integer can be converted to a pointer (which implies a
specific syntax, like casting to an int poiner). This pointer can then be
used to access memory, but it might not work.

This is just silly... you have a mechanism for converting
between pointers and integers that may or may not work, for any given
combination of platform, compiler and the values you try to
convert. This is neither portable or dependable. Further, even if it
did work consistently it might not do what you wanted - for example,
in the presence of a memory mapping unit.

I think you'll find that (most?) operating systems provide
low-level calls for direct access to memory that takes care of all
the details, including bypassing the MMU. In some cases, the calls may
even have been open-coded in the STANDARD compiler used with that os.

This is of course just as true for an OS written in LISP as in
C :-)

.



Relevant Pages

  • Re: Python syntax in Lisp and Scheme
    ... Lisp also has this to a certain degree: ... what language "paradigm" you are currently using. ... > conjecture is that additional syntax can make some things easier. ... I don't know a lot about the specifics of shared memory, ...
    (comp.lang.python)
  • Re: Python syntax in Lisp and Scheme
    ... Lisp also has this to a certain degree: ... what language "paradigm" you are currently using. ... > conjecture is that additional syntax can make some things easier. ... I don't know a lot about the specifics of shared memory, ...
    (comp.lang.lisp)
  • Re: Dynamic function generation, HOW?
    ... I will try to concentrate more on the conceptual model of lisp, ... garbage collectors: ... Conservatives garbage collectors scan the memory and whatever bit ... pattern that looks like a pointer is considered to be a pointer to ...
    (comp.lang.lisp)
  • Re: Comparing pointers to NULL
    ... Had I designed the language from the beginning, I would have used the syntax ... of [pointer] for all pointer dereference. ... So if you think of 0 as being a reference to all of memory itself, ...
    (comp.lang.c)
  • Re: f95 OOP question
    ... pointer to a third one. ... It goes something like this (I am writing from memory, so the syntax is not quite right), and I have not managed to get it to compile yet: ...
    (comp.lang.fortran)