From: Fletcher T. Penney Date: Mon, 20 Nov 2017 19:47:12 +0000 (-0500) Subject: version bump X-Git-Tag: 6.2.3^2 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5381140c2bfd880db6704f3e8f596178a5d26e52;p=multimarkdown version bump --- diff --git a/CMakeLists.txt b/CMakeLists.txt index 5e7ca42..7bd9f10 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -8,10 +8,10 @@ cmake_minimum_required (VERSION 2.6) set (My_Project_Title "MultiMarkdown") set (My_Project_Description "Lightweight markup processor to produce HTML, LaTeX, and more.") set (My_Project_Author "Fletcher T. Penney") -set (My_Project_Revised_Date "2017-10-13") +set (My_Project_Revised_Date "2017-11-20") set (My_Project_Version_Major 6) set (My_Project_Version_Minor 2) -set (My_Project_Version_Patch 2) +set (My_Project_Version_Patch 3) set (My_Project_Version "${My_Project_Version_Major}.${My_Project_Version_Minor}.${My_Project_Version_Patch}") diff --git a/DevelopmentNotes/DevelopmentNotes.epub b/DevelopmentNotes/DevelopmentNotes.epub index 6777b1f..dbf317a 100644 Binary files a/DevelopmentNotes/DevelopmentNotes.epub and b/DevelopmentNotes/DevelopmentNotes.epub differ diff --git a/DevelopmentNotes/DevelopmentNotes.fodt b/DevelopmentNotes/DevelopmentNotes.fodt index 1be40f8..8e071cc 100644 --- a/DevelopmentNotes/DevelopmentNotes.fodt +++ b/DevelopmentNotes/DevelopmentNotes.fodt @@ -276,7 +276,7 @@ office:mimetype="application/vnd.oasis.opendocument.text"> MultiMarkdown v6 Development Notes Fletcher T. Penney - 2017-10-13 + 2017-11-20 dd2d8e76-dc2d-416d-9acd-5395d20871c2 @@ -531,7 +531,7 @@ added up and slowed down performance. After reading for a bit, I ended up coming up with an approach that uses larger chunks of memory. I allocate pools of of memory in large slabs for -smaller “objects”". For example, I allocate memory for 1024 tokens at a +smaller "objects. For example, I allocate memory for 1024 tokens at a single time, and then dole that memory out as needed. When the slab is empty, a new one is allocated. This dramatically improved performance. @@ -566,7 +566,7 @@ measurable difference. I experimented with different approaches to creating the output after parsing. I tried printing directly to stdout, and even played with different buffering settings. None of those seemed to work well, and all were slower -than using the d_string approach (formerly call GString in MMD 5). +than using the d_string approach (formerly called GString in MMD 5). Fast Searches @@ -684,10 +684,10 @@ application with every release. Fuzz Testing -I was not familiar with the concept of Fuzz Testing -(https://en.wikipedia.org/wiki/Fuzzing) until a user mentioned something about -it to me a year or two ago. I had never used it before, but it seemed like a -good idea. I implement it in two ways. +I was not familiar with the concept of +Fuzz Testing until a user mentioned +something about it to me a year or two ago. I had never used it before, but +it seemed like a good idea. I implemented it in two ways. The first is that I created a simplified version of the line parser that simply accepts various combinations of line type identifiers to see if they @@ -702,13 +702,13 @@ several combinations of lines that did not pass. NOTE: This does not verify accurate parsing, simply that the parser does not crash by an unacceptable combination of lines. -The second form of fuzz testing I have started using more recently. This is -using the American fuzzy lop program to try -to find text input that crashes MMD. This works by taking sample input (e.g. -files from the test suite), modifying them slightly, and trying the modified +The second form of fuzz testing I started using later. This is using the +American fuzzy lop program to try to find +text input that crashes MMD. This works by taking sample input (e.g. files +from the test suite), modifying them slightly, and trying the modified versions. Do this over and over and over, and some interesting edge cases are sometimes identified. I have found some interesting edge cases this way. -Definitely a very useful tool! +Definitely a useful tool! Unit Testing @@ -762,6 +762,67 @@ TextBundle/TextPack, OpenDocument, etc. Changelog + +2017–11–20 - v 6.2.3: + + + + +CHANGED: Fix typos + + + +CHANGED: Update superscript/subscript algorithm to allow leading instances + + + +FIXED: Fix bug with multiple footnotes in single paragraph when exporting to LaTeX + + + +FIXED: Fix potential NULL pointer dereference + + + +FIXED: Fix potential bug + + + +FIXED: Prevent pointer overflow + + + +FIXED: Strip UTF-8 BOM from main files, not just transcluded files + + + +UPDATED: Add HTML comment test cases to further demonstrate + + + +UPDATED: Adjust libMultiMarkdown.h so it does not recursively include other files + + + +UPDATED: Fix issue with AStyle indent settings + + + +UPDATED: Refactor file utilities into file.c/h + + + +UPDATED: Silence Xcode static analyzer false positives + + + +UPDATED: Silence analyzer warnings + + +UPDATED: Update function name in swift file + + + 2017–10–13 - v 6.2.2.: diff --git a/DevelopmentNotes/DevelopmentNotes.html b/DevelopmentNotes/DevelopmentNotes.html index f739ee7..ea75578 100644 --- a/DevelopmentNotes/DevelopmentNotes.html +++ b/DevelopmentNotes/DevelopmentNotes.html @@ -4,7 +4,7 @@ MultiMarkdown v6 Development Notes - + @@ -209,7 +209,7 @@ added up and slowed down performance.

After reading for a bit, I ended up coming up with an approach that uses larger chunks of memory. I allocate pools of of memory in large slabs for -smaller “objects”". For example, I allocate memory for 1024 tokens at a +smaller "objects. For example, I allocate memory for 1024 tokens at a single time, and then dole that memory out as needed. When the slab is empty, a new one is allocated. This dramatically improved performance.

@@ -244,7 +244,7 @@ measurable difference.

I experimented with different approaches to creating the output after parsing. I tried printing directly to stdout, and even played with different buffering settings. None of those seemed to work well, and all were slower -than using the d_string approach (formerly call GString in MMD 5).

+than using the d_string approach (formerly called GString in MMD 5).

Fast Searches

@@ -362,10 +362,10 @@ application with every release.

Fuzz Testing

-

I was not familiar with the concept of Fuzz Testing -(https://en.wikipedia.org/wiki/Fuzzing) until a user mentioned something about -it to me a year or two ago. I had never used it before, but it seemed like a -good idea. I implement it in two ways.

+

I was not familiar with the concept of +Fuzz Testing until a user mentioned +something about it to me a year or two ago. I had never used it before, but +it seemed like a good idea. I implemented it in two ways.

The first is that I created a simplified version of the line parser that simply accepts various combinations of line type identifiers to see if they @@ -380,13 +380,13 @@ several combinations of lines that did not pass.

NOTE: This does not verify accurate parsing, simply that the parser does not crash by an unacceptable combination of lines.

-

The second form of fuzz testing I have started using more recently. This is -using the American fuzzy lop program to try -to find text input that crashes MMD. This works by taking sample input (e.g. -files from the test suite), modifying them slightly, and trying the modified +

The second form of fuzz testing I started using later. This is using the +American fuzzy lop program to try to find +text input that crashes MMD. This works by taking sample input (e.g. files +from the test suite), modifying them slightly, and trying the modified versions. Do this over and over and over, and some interesting edge cases are sometimes identified. I have found some interesting edge cases this way. -Definitely a very useful tool!

+Definitely a useful tool!

Unit Testing

@@ -432,6 +432,24 @@ TextBundle/TextPack, OpenDocument, etc.

Changelog

    +

  • 2017–11–20 - v 6.2.3:

    + +
      +
    • CHANGED: Fix typos
      • +
    • CHANGED: Update superscript/subscript algorithm to allow leading instances
      • +
    • FIXED: Fix bug with multiple footnotes in single paragraph when exporting to LaTeX
      • +
    • FIXED: Fix potential NULL pointer dereference
      • +
    • FIXED: Fix potential bug
      • +
    • FIXED: Prevent pointer overflow
      • +
    • FIXED: Strip UTF-8 BOM from main files, not just transcluded files
      • +
    • UPDATED: Add HTML comment test cases to further demonstrate
      • +
    • UPDATED: Adjust libMultiMarkdown.h so it does not recursively include other files
      • +
    • UPDATED: Fix issue with AStyle indent settings
      • +
    • UPDATED: Refactor file utilities into file.c/h
      • +
    • UPDATED: Silence Xcode static analyzer false positives
      • +
    • UPDATED: Silence analyzer warnings
      • +
    • UPDATED: Update function name in swift file
      • +

  • 2017–10–13 - v 6.2.2.:

      diff --git a/DevelopmentNotes/DevelopmentNotes.pdf b/DevelopmentNotes/DevelopmentNotes.pdf index 9f544bc..813636e 100644 Binary files a/DevelopmentNotes/DevelopmentNotes.pdf and b/DevelopmentNotes/DevelopmentNotes.pdf differ diff --git a/DevelopmentNotes/DevelopmentNotes.txt b/DevelopmentNotes/DevelopmentNotes.txt index ac02f1d..45ad918 100644 --- a/DevelopmentNotes/DevelopmentNotes.txt +++ b/DevelopmentNotes/DevelopmentNotes.txt @@ -1,6 +1,6 @@ Title: MultiMarkdown v6 Development Notes Author: Fletcher T. Penney -Date: 2017-10-13 +Date: 2017-11-20 LaTeX Config: tufte-handout Base Header Level: 3 uuid: dd2d8e76-dc2d-416d-9acd-5395d20871c2 @@ -471,6 +471,24 @@ TextBundle/TextPack, OpenDocument, etc. # Changelog # +* 2017-11-20 - v 6.2.3: + + * CHANGED: Fix typos + * CHANGED: Update superscript/subscript algorithm to allow leading instances + * FIXED: Fix bug with multiple footnotes in single paragraph when exporting to LaTeX + * FIXED: Fix potential NULL pointer dereference + * FIXED: Fix potential bug + * FIXED: Prevent pointer overflow + * FIXED: Strip UTF-8 BOM from main files, not just transcluded files + * UPDATED: Add HTML comment test cases to further demonstrate + * UPDATED: Adjust libMultiMarkdown.h so it does not recursively include other files + * UPDATED: Fix issue with AStyle indent settings + * UPDATED: Refactor file utilities into file.c/h + * UPDATED: Silence Xcode static analyzer false positives + * UPDATED: Silence analyzer warnings + * UPDATED: Update function name in swift file + + * 2017-10-13 - v 6.2.2.: * ADDED: Add support for tables without header; test for table with multiple header rows diff --git a/README.md b/README.md index 9d7b680..5f64b52 100644 --- a/README.md +++ b/README.md @@ -4,9 +4,9 @@ | ---------- | ------------------------- | | Title: | MultiMarkdown | | Author: | Fletcher T. Penney | -| Date: | 2017-10-13 | +| Date: | 2017-11-20 | | Copyright: | Copyright © 2016 - 2017 Fletcher T. Penney. | -| Version: | 6.2.2 | +| Version: | 6.2.3 | master branch: [![Build Status](https://travis-ci.org/fletcher/MultiMarkdown-6.svg?branch=master)](https://travis-ci.org/fletcher/MultiMarkdown-6) develop branch: [![Build Status](https://travis-ci.org/fletcher/MultiMarkdown-6.svg?branch=develop)](https://travis-ci.org/fletcher/MultiMarkdown-6)