#define MAXBITS 15
#define MAXLCODES 286
#define MAXDCODES 30
#define MAXCODES
#define FIXLCODES 288
struct state
local int bits(struct state *s, int need)
local int stored(struct state *s)
struct huffman
local int decode(...)
local int construct(...)
local int codes(...)
local int fixed(...)
local int dynamic(...)
int puff(...)
It was my joke, at the top of this thread and the only one in this thread. Have you considered the possibility that you have no idea what is going on here (your lack of fluency in English is a likely factor) and that you have no business poking your nose into it, person who is attacking me with a hostile rhetorical question for no good reason? The fact is that I do put quite a bit of effort into being sure that I understand the context--a lot more effort than you and others here have.
He probably misuses "propeller" which is strangely restrictive to "rotative blade propulsion" in English whereas "to propel" is generic in its meaning.
Inflammable made me so angry as a child/teen when I found out. I read it in our encyclopedia set but we didn't have a dictionary, and this was pre-internet.
It was in the context of hydrogen and I could have sworn it was flammable. But here is this encyclopedia telling me it's INflammable. It's... not flammable? Looked it up in the school library.
Thank you, that memory came up from the depths of time. Probably haven't thought about that in 30 years. Funny how we sometimes just didn't know stuff, and couldn't find out back then.
It's just a parsing error. "in-" is also a prefix to create verbs from a name or another verb like inhume, inflame, induce, incite, inject, infiltrate. Inflammable is (inflame)-able and not in-(flammable)
There are many counter-examples to your examples, such as “direct” and “indirect”, “humane” and “inhumane”.
The words used should be clear in their meaning. “Inflammable” is ambiguous, and it makes a great deal of difference which meaning is intended.
Flammable is unambiguous, as is non-inflammable. I’m forced to use these. Personally, I’m more in favour of flammable (able to catch fire) and inflammable (not able to catch fire).
There's an inconsistency but no ambiguity, only ignorance. Inflammable only ever means one thing regardless of how ridiculous english might be.
The historically correct term would be non-inflammable. The modern variant is non-flammable.
Similarly, inflammable is the historic term and flammable is the modern variant.
The confusion arises when people are exposed to the word flammable and then attempt to apply the usual rules to construct a word they've never actually used before.
This isn't the usual sort of inconsistency introduced by our fusing multiple incompatible languages. It's from the original Latin and I'm unclear what led to it. For example consider inflammable versus inhumane. It seems Latin itself used the prefix to mean different things - here on(fire) versus not(human). But confusingly it's ex to indicate location, despite ex also being the antonym of in. So ex equo means you are on horseback, not off it as I would have guessed.
> There are many counter-examples to your examples, such as “direct” and “indirect”, “humane” and “inhumane”.
They are not counter-example. You use the other "in-" prefix that take an adjective and give the opposite adjective, not the one that create a verb from a noun.
So does getting infected over and over. Much worse damage. Evolution isn't some magic thing that gives you the most optimal creature for a given metric. The only metric is procreation. Not longevity. Not a pleasant life.
The fact that he calls the generated code good/bad without discussing the semantic differences tells that the original author doesn't really know what he is talking about. That seems problematic to me as he is selling c++ online course.
If you go on particular laws, you can see the previous versions and how it changed. Example: https://www.legifrance.gouv.fr/codes/section_lc/LEGITEXT0000...
Click on "version" then "comparer" buttons and you will see a diff.
reply