Definitely a Lisp language. Like Common Lisp or Racket or Clojure.
> It has no notion of virtual or physical memory. Exactly! That's why once virtual memory is allocated, malloc() is allowed to consider the operation successful. The standard does not care at all whether it is virtual…
The malloc() function requests memory from the kernel using mmap(). If mmap() returns successfully, it means that the kernel is saying that the memory is allocated. So from malloc()'s perspective the memory allocation…
You can't be serious about "every part". This definitely does not violate section 1.1 which only talks about the scope of the standard. It also definitely does not violate 1.2 which talks about what is not within the…
> I find it surprising how we have a functioning society with such underfinanced and overworked police, even in the well to do urban areas. At the risk of being downvoted, I feel compelled to offer a foreigner's…
Definitely a Lisp language. Like Common Lisp or Racket or Clojure.
> It has no notion of virtual or physical memory. Exactly! That's why once virtual memory is allocated, malloc() is allowed to consider the operation successful. The standard does not care at all whether it is virtual…
The malloc() function requests memory from the kernel using mmap(). If mmap() returns successfully, it means that the kernel is saying that the memory is allocated. So from malloc()'s perspective the memory allocation…
You can't be serious about "every part". This definitely does not violate section 1.1 which only talks about the scope of the standard. It also definitely does not violate 1.2 which talks about what is not within the…
> I find it surprising how we have a functioning society with such underfinanced and overworked police, even in the well to do urban areas. At the risk of being downvoted, I feel compelled to offer a foreigner's…