enlightenment/www-content
enlightenment
/
www-content
6
0
Fork 2
Code Issues Pull Requests 1 Projects Releases Wiki Activity

??

This commit is contained in:
apache 2017-10-18 14:57:33 -07:00
parent ee5eafa303
commit 20d7d36f4c
2 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pages/about-ephoto.txt
View File

@ -10,11 +10,9 @@ Ephoto is an image viewer and editor written using the Enlightenment Foundation
<clear/>
=== Screenshots ===
{{:shot-2017-08-22_07-52-53.jpg?400|}}
{{:shot-2017-08-22_07-54-31.jpg?400|}}
{{:shot-2017-08-22_07-53-57.jpg?400|}}
{{:shot-2017-08-22_07-52-53.jpg?400 |}}
{{:shot-2017-08-22_07-54-31.jpg?400 |}}
{{:shot-2017-08-22_07-53-57.jpg?400 |}}
<clear/>

2
pages/docs/c/start.txt
View File

@ -434,7 +434,7 @@ So only compile the active code in when enabled in the compilation process.
==== Memory ====
Reality is that languages like C are really a slightly more convenient and portable interface to the actual machine you have. That means the CPU, it's instructions and processing as well as memory that the CPU will access one way or another. Let's visualize just some of this. Imagine memory as simply a series of boxes than can contain a number that has a value from 0 to 255 (if unsigned). To do signed values we just interpret values differently. We can have from -128 to 127 as values. When you hit the maximum value, things wrap around to the minimum. For signed and unsigned the first 128 values are the same in memory. This also is true for shorts, ints, longs and long longs, except it is the lower positive half of the range. To make life easier for computers, we will use [[http://en.wikipedia.org/wiki/Hexadecimal|hexadecimal]] to represent the numbers as raw data (no sign is implied here).
Reality is that languages like C are really a slightly more convenient and portable interface to the actual machine you have. That means the CPU, its instructions and processing as well as memory that the CPU will access one way or another. Let's visualize just some of this. Imagine memory as simply a series of boxes than can contain a number that has a value from 0 to 255 (if unsigned). To do signed values we just interpret values differently. We can have from -128 to 127 as values. When you hit the maximum value, things wrap around to the minimum. For signed and unsigned the first 128 values are the same in memory. This also is true for shorts, ints, longs and long longs, except it is the lower positive half of the range. To make life easier for computers, we will use [[http://en.wikipedia.org/wiki/Hexadecimal|hexadecimal]] to represent the numbers as raw data (no sign is implied here).
^Byte ^Value ^
|0 |01 |