pixelglow
Joined 18 years ago
Joined 18 years ago
The only wrinkle is that each entry has a header which typically states the compressed size and checksum. Either you have to compress each entry content in some temp buffer or file to figure out the compressed size and checksum, then write out the header and compressed content. Or you write out the header with these fields zeroed, then compress the content on the fly and write it out, then write out a data descriptor with the compressed size and checksum.
In particular, in the beginning Objective-C was a lot looser typed at compile time than it is now: no NSString* or NSWindow*, it was all just id. It was an attempt to make C look like Smalltalk.
The language eventually evolved more toward the static-typed end of the spectrum, culminating in support for lightweight generics and ostensibly birthing Swift along the way.
I'm not a doctor however so take any advice with a grain of salt. (But not sugar, definitely not that.)
> I keep reading that the problem is carbohydrate overload to my genetics.
Read up on "glycemic index". This index tells you how close your food is to pure glucose e.g. table sugar has a glycemic index of 68 so it has 68% of the insulin response of pure glucose. The index correlates to the type of carbohydrate and how processed it is, although there are some surprises e.g. premium ice cream has a G.I. of 37.
http://www.glycemicindex.com/index.php
You don't have to commit the entire index to memory. Usually you can come up with several heuristics e.g. tropical fruit tends to have higher G.I. than temperate fruit.
Obviously you should test this with your own blood sugar readings as individual response to a carbohydrate challenge can be quite different.
The other components to a meal also affect blood sugar. For example, acid, protein and fat tend to slow down digestion and thus blood sugar spiking. If you must take pasta for example, take it with a tomato-based sauce (acidic) rather than cream-based. YMMV.
> Unfortunately, my doctor thinks that pushing pills is an adequate response, which I heartily doubt.
It's important, although somewhat depressing, to see this disease as a progression. A progression that you have to slow down as much as possible, but still a progression.
Know that in the future, you may have to resort to the first line of pills, and then possibly stronger ones. Try to slow down the progression as much as possible, and research the pills to see their efficacy and benefit.
Metformin is usually the first line of defence and it has a long history and little side effect. It generally fools your body into thinking it's in starvation mode, which means you can lose weight, both fat and muscle. It actually lowers insulin resistance rather than increasing insulin. Generally in amounts >1g it gives you loose bowels, so when you have to use it keep on low doses as long as possible.
When metformin doesn't work as well, generally you'll get prescribed sulfonylureas. Since they increase insulin secretion, they tend to exacerbate your insulin resistance. There is some inconclusive research that they burn out the pancreatic beta cells. Better to avoid these as long as possible, but if your glucose control is bad you may not have a choice.
I'm currently on an incretin enhancer (gliptin) + metformin.
Also look up supplements on examine.com. It's hard to tell the effectiveness of supplements, the only one that had a distinct effect on me was berberine.
The other thing you can do is exercise. Lots of it. Strength training for more muscle and more insulin receptors. Aerobic exercise to burn/absorb more glucose and lose weight. There's even recent evidence that high-intensity interval training improves diabetic markers more than sustained, low-intensity exercise.
You could
* Combine it with black pepper, warmth and/or oil.
* Use the Meriva or BCM-95 form.
* Use nanoparticles, marketed as Theracurmin/Theracumin.
Most nights, I combine two caps of Theracurmin with fish oil and lukewarm water for my wife to drink. It does seem to help with her arthritis.
I suspect this originated with autistic individuals finding it hard to actually lie, i.e deceive. This relates to their shallow theory of mind, or difficulty believing other people have different thoughts and ideas from them or the absolute "truth". This idea has subtly spread through science and tech culture since many practitioners are on the spectrum, where some absolute truth is held up for admiration and significant deviation is uncomfortable.
For example, "code never lies." So if I say "xyz" about the code and it is false, I am "lying".
http://stackoverflow.com/a/12393597/60910
Therefore the straightforward way to parse a zip file is to proceed from the beginning and parse out each file sequentially. The End of Central Directory record is then only a redundant convenience to avoid sequentially scanning files e.g. in large zips for random access.