Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

17
  • 17
    Do you print to a window? or a console? or to graphics memory? How do you put the data there? Looking at printf for Apple][+ would be quiet different than for a Mac OS 7 and again quite different than Mac OS X (just sticking with one 'line' of computers). Commented Jul 8, 2014 at 2:10
  • 4
    Because if you wrote that code for Mac OS 7, it would show up in text in a new window. If you did it on Apple ][+, it would be writing to some segment of memory directly. On Mac OS X, it writes it out to a console. Thus, thats three different ways of writing handling the code based on the execution hardware that is handled by the library layer. Commented Jul 8, 2014 at 3:45
  • 2
    @StevenBurnap yep - en.wikipedia.org/wiki/Aztec_C Commented Jul 8, 2014 at 3:59
  • 11
    Your FFT function will happily run under Windows or Linux (on the same CPU), without even recompiling. But then how are you going to display the result? Using an operating system API, of course. (printf from msvcr90.dll is not the same as printf from libc.so.6) Commented Jul 8, 2014 at 6:53
  • 9
    Even if APIs are "not part of the operating system", they are still different if you go from one OS to the other. (Which, of course, raises the question of what the phrase "not part of the operating system" really means, according to the diagram.) Commented Jul 8, 2014 at 10:21