Talk:Machine code: Difference between revisions
Content added Content deleted
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
* "[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.) |
* "[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." |
* "Don't require exceedingly rare features." |
||
--[[User:Ttmrichter|Michael T. Richter]] ([[User talk:Ttmrichter|talk]]) 00:34, 14 January 2014 (UTC) |
|||
Revision as of 00:34, 14 January 2014
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)