Finish reorganization

[mildsunrise]

Now that @devinus has done the base work,
there's still some things to do, namely:

Code (3)

• Prefix enums as well. Currently they start with
    MKD_ or HTML_.
• Normalize guard names and comments on headers.
• General cleanup.

Building and versioning (4)

• Remove the html/ directory from Makefiles.
• Makefile.win should be modified as well.
• Add everything to hoedown.def.
• Reset version.

Readme and licensing (5)

• Correct a typo at README.
• Review the README. Especially clarify the "bindings" part:
  all those bindings currently aren't Hoedown bindings.
• Rewrite the "Install" section. The "it's just three files" part
  is not true anymore.
• Does README's License match with LICENSE?
• Update preambles where necessary.

[mildsunrise]

I'm creating a wiki page to list the [future] bindings, and referencing it from README.

@devinus, you should also change the "Help us" section, I don't know what to put in there.

[devinus]

markdown.{c,h} should be left as is. This is because its name expresses what part of Sundown/Hoedown is (in that case, the Markdown parser). Hoedown is comprised of all the sources, not just the Markdown parsing part.
Same for buffer.{c,h}. We want to keep things simple, so if the user wants to group Hoedown sources he can just put them in a hoedown folder, and then #include "hoedown/markdown.h" (to use the Markdown parser) or #include "hoedown/escape.h" (to use just the houdini part).

I agree. I changed my mind last night too.

Prefix enums as well. Currently they start with MKD_ or HTML_

Agreed. The only reason I didn't do it last night is because I wanted to figure out what to name the MKD_EXT_* values. HOEDOWN_MKD_EXT_* is a little too long. I for sure want them prefixed with HOEDOWN_* but at the minimum they should become HOEDOWN_MD_EXT_* or HOEDOWN_EXT_*. HOEDOWN_EXT_* is currently winning me over since some extensions aren't even general Markdown extensions you see elsewhere, just stuff that the Redcarpet team liked.

[mildsunrise]

I'm totally going for the HOEDOWN_EXT_* choice.
And for the HTML_* ones, HOEDOWN_HTML_*.

[devinus]

👍

[mildsunrise]

Also I'm going to remove most of the "Credits" section;
it's mostly incomplete and it doesn't belong there.

[mildsunrise]

Can I remove the preambles on Makefile and examples/?
I suppose so.

[devinus]

Please do.

[devinus]

Can you also update the LICENSE to say:

Copyright (c) 2013, Devin Torres and the Hoedown authors

Or I can do it later tonight.

[mildsunrise]

I will do it.

[mildsunrise]

Done, only two tasks left.

[mildsunrise]

I did it! I managed to refactor every enum!
It builds correctly. Look at the three commits.

[devinus]

Excellent! I plan to benchmark the branch prediction Houdini added later today and see if it's worth it.

[mildsunrise]

Goodie! 😃

[mildsunrise]

One thing I'd also like to do is to reformat the code
to a two-space indentation, as the Google Style
Guide says.

Currently there's a mix of tabs, 8 spaces and 4 spaces,
sometimes even on the same file.

[devinus]

@jmendeth There's only a few places where spaces are used (I did a grep -R " "). We could clean those up, but I'm not sure about changing the indentation at this point.

Rationale: While I hate tab indentation (seriously, who still uses tabs?) and love me some two space indentation, we would clobber all git blame functionality forever. :(

[mildsunrise]

Uhm, yeah, I understand you.
But if you think about it, we have already clobbered it
with all these backporting, name changing, cleanup, etc.

[mildsunrise]

But if you don't want, that's fine, it's not a must-have for me.

I have to go to the bed (or my parents'll kill me)
so I'll finish this PR tomorrow.

[devinus]

Well, thankfully the name changing would only affect lines that used an exposed interface. I'm more concerned with blocks like this:

            if (i < lang->size) {
                size_t org = i;
                while (i < lang->size && !isspace(lang->data[i]))
                    i++;

                if (lang->data[org] == '.')
                    org++;

...which hasn't been clobbered yet, and if it came from a backport we have a clear history on it since I took the time to keep it.

We can and should discuss coding style though, but definitely in another issue.

[mildsunrise]

No, I definitively don't want to spend time debating this aspect. ;)
At least for now. Good night!

[devinus]

Is this ready?

[mildsunrise]

All ready! It includes your latest changes
and it builds without a warning.

[mildsunrise]

Weeeee!