[gmime] Avoid API breakage of GMimeParserWarning (#42)



commit f016b310a37ea8551e630ef5827c319f8a8f984e
Author: dkg <dkg fifthhorseman net>
Date:   Thu Jan 18 06:57:38 2018 -0500

    Avoid API breakage of GMimeParserWarning (#42)
    
    in 14671817dc1a64d8840b2f612cd143f29d55ecbf,
    GMIME_WARN_INVALID_PARAMETER was introduced, but it also changed the
    enum values for every GMimeParserWarning that followed it in the list.
    
    This means that if someone built against a prior version of GMime and
    then upgraded their library, the library might try to return, say,
    GMIME_CRIT_CONFLICTING_HEADER but the application would interpret it
    as GMIME_CRIT_CONFLICTING_PARAMETER.
    
    This change restores the original API for GMimeParserWarning, since
    there is probably already released and distributed software built
    against the older header files.

 gmime/gmime-parser-options.h |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/gmime/gmime-parser-options.h b/gmime/gmime-parser-options.h
index 4e5a747..a8dedbe 100644
--- a/gmime/gmime-parser-options.h
+++ b/gmime/gmime-parser-options.h
@@ -66,14 +66,14 @@ typedef enum {
        GMIME_WARN_UNENCODED_8BIT_HEADER,
        GMIME_WARN_INVALID_CONTENT_TYPE,
        GMIME_WARN_INVALID_RFC2047_HEADER_VALUE,
-       GMIME_WARN_INVALID_PARAMETER,
        GMIME_WARN_MALFORMED_MULTIPART,
        GMIME_WARN_TRUNCATED_MESSAGE,
        GMIME_WARN_MALFORMED_MESSAGE,
        GMIME_CRIT_INVALID_HEADER_NAME,
        GMIME_CRIT_CONFLICTING_HEADER,
        GMIME_CRIT_CONFLICTING_PARAMETER,
-       GMIME_CRIT_MULTIPART_WITHOUT_BOUNDARY
+       GMIME_CRIT_MULTIPART_WITHOUT_BOUNDARY,
+       GMIME_WARN_INVALID_PARAMETER
 } GMimeParserWarning;
 
 /**


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]