go
/
bindata
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Minor cleanup of README.

pull/4/head
jimt 2013-03-09 13:37:09 +01:00
parent b6af78b318
commit 0877d93299
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -56,7 +56,7 @@ The default behaviour is to use the old code generation method. This
prevents the two previously mentioned issues, but will employ at least one
extra memcopy and thus increase memory requirements.
For instance, consider the following two examples...
For instance, consider the following two examples:
This would be the default mode, using an extra memcopy but gives a safe
implementation without dependencies on `reflect` and `unsafe`:
@ -65,7 +65,7 @@ implementation without dependencies on `reflect` and `unsafe`:
return []byte{0x89, 0x50, 0x4e, 0x47, 0x0d, 0x0a, 0x1a}
}
Here is the same functionality, but uses the .rodata hack.
Here is the same functionality, but uses the `.rodata` hack.
The byte slice returned from this example can not be written to without
generating a runtime error.