jim teeuwen
|
98c1704190
|
Combine the old and new code generation methods. We can select the .rodata hack described in issue #1 by supplying the -m commandline flag. The default code generation mode is the old one. While it uses more memory, it is a safer version and offers no problems when used on platforms that restrict usage of the unsafe and reflect packages. Additionally I did some cleanup and refactoring of the code. Bumped version to 1.0.0
|
2012-06-22 14:12:15 +02:00 |
|
jim teeuwen
|
37af2a4b27
|
Fix generated code for both compressed and uncompressed modes. We now no longer require a memcpy to read the static file data and can get it directly from the .rodata section. This addresses issue #1
|
2012-06-13 14:17:25 +02:00 |
|
jim teeuwen
|
384e0cafe9
|
Added -u flag. When this is supplied to the program, no compression of the input data will take place. This also means the generated source code changes from a function to a global variable. The function is only there because it has to decompress the binary data. When no compression is used, this is obviously not necessary. Default behaviour is still the same (with compression) so existing code using this program will not break. Fixed README to reflect new behaviour. Added new testdata examples for both compressed and uncompressed output.
|
2012-03-28 01:39:01 +02:00 |
|
jim teeuwen
|
0450ba8421
|
Change signature of generated function to only return the decompressed byte slice. The error value is removed. Instead the function will panic when a decompression error occurs. This allows us to assign the data to global variables were necessary. A decompression error is considered a deal breaker and therefor the panic is warranted.
|
2012-03-08 11:47:57 +01:00 |
|
jim teeuwen
|
360acac596
|
Update README to reflect fix in generated file.
|
2012-03-06 19:31:58 +01:00 |
|
jim teeuwen
|
02da4740e4
|
Fix generate doutput code. os.Error -> error. Remove calling of go fmt from code. This should really be done manually.
|
2012-02-11 16:49:43 +01:00 |
|