Commits on Jan 23, 2015
  1. Merge pull request #2 from steve-m-hay/master

    Remove needless and potentially harmful #ifdef _cplusplus extern "C"
    committed Jan 23, 2015
  2. Remove needless and potentially harmful #ifdef _cplusplus extern "C"

    When building core perl, and hence MIME-Base64, in C++ mode on Windows
    the #include of perl's headers within an extern "C" { ... } forces
    unmangled symbol names to be referenced in the perlXXX.dll, but due to
    a current bug in the C++ mode build of perl a few symbols actually
    appear with mangled names, causing a linker failure in MIME-Base64.
    The C++ mode build on Windows is currently a work in progress and
    hopefully the mangled names bug will be fixed in due course, but I do
    not see any benefit in MIME-Base64 #including the headers in extern "C"
    anyway. In a C mode build the extern "C" thing isn't done due to the
    #ifdef; in a C++ mode build it works if perl is correctly built with
    unmangled names but otherwise just causes breakage when things would
    have worked fine without it (since without it, MIME-Base64 will simply
    reference the same (currently mangled) symbol name that perl is
    There are a few other XS modules in the core which have a similar
    extern "C" thing around the #includes, but the vast majority do not.
    Unless you know of a specific reason for having it then I think it
    would be better off without it. It has been present in MIME-Base64
    ever since the first revision of Base64.xs:
    There is a thread on perl5-porters regarding this. See the end of
    this message in particular:
    steve-m-hay committed Jan 23, 2015
Commits on Jan 12, 2015
  1. Release 3.15

    committed Jan 12, 2015
  2. Compatibility with older perls [RT#30347]

    XSLoader is now on CPAN, it works on perl 5.4.
    Alexandr Ciornii committed with Jan 12, 2015
  3. Merge pull request #1 from dolmen/patch-1

    committed Jan 12, 2015
  4. MIME::Base64: fix a couple of compiler warnings

    A win32 smoker is showing:
    Base64.xs(394) : warning C4146: unary minus operator applied to unsigned type,
    result still unsigned
    Base64.xs(396) : warning C4146: unary minus operator applied to unsigned type,
    result still unsigned
    Since I don't run windows, I can't yet confirm whether this commit
    actually silences the warnings.
    iabyn committed with Dec 19, 2014
Commits on Jul 2, 2013
  1. Release 3.14

    committed Jul 2, 2013
Commits on May 15, 2013
  1. s{http://github}{https://github}

    Fix Github link as https
    dolmen committed May 15, 2013
Commits on Jan 7, 2011
Commits on Nov 26, 2010
  1. Release 3.13

    committed Nov 26, 2010
Commits on Nov 25, 2010
  1. Release 3.12

    committed Nov 25, 2010
  2. Documenation tweak

    committed Nov 25, 2010
Commits on Nov 24, 2010
  1. Copyright 2010

    committed Nov 24, 2010
  2. Silence 'git status'

    committed Nov 24, 2010
  3. Release 3.11

    committed Nov 24, 2010
  4. No need to decode from the byte representation of a base64 string

    When we don't utf8_downgrade we might end up decoding the utf8
    representation of the string, but since we just ignore anything
    that's not ASCII it does not matter.
    committed Nov 24, 2010
Commits on Nov 23, 2010
Commits on Nov 11, 2010
  1. Release 3.10

    committed Nov 11, 2010
Commits on Oct 25, 2010
Commits on Jan 25, 2010
  1. Release 3.09

    committed Jan 25, 2010
Commits on Jun 10, 2009
  1. consting in new ext/

    Robin Barker committed with Feb 10, 2009
Commits on Jun 9, 2009
  1. Release 3.08

    committed Jun 9, 2009