Talk:Machine code

From Rosetta Code
Revision as of 13:17, 2 December 2014 by rosettacode>Bearophile (+ note to D entry)

This nice task still awaits your contributions (at least 4).

I'm pretty sure this task isn't going to get a lot of love because:

  • It's architecture-specific.
  • It's for a technique that few people use these days in the era of inline assembler, etc.
  • It's only really usable for low-level languages (and yes, this includes Lisp: Lisp is a low level language that can be easily built up into high levels).
  • It assumes C calling conventions in its very structure.

Quoting some of the guidelines:

  • "[The] goal is to address a problem a programmer may face or want to think about" (I'm pretty sure the age of BASIC programmers POKEing and PEEKing their C64s is long past.)
  • "Don't require exceedingly rare features."

--Michael T. Richter (talk) 00:34, 14 January 2014 (UTC)

D entry

In D, unlike in C, I have performed just a function cast on the memory of the array. Is the memory mapping used in the C entry for portability with operating systems that disallow such operation for safety?

Retrieved from "https://rosettacode.org/wiki/Talk:Machine_code?oldid=237941"