1. 16 May, 2019 2 kayıt (commit)
  2. 10 May, 2019 1 kayıt (commit)
  3. 31 Mar, 2019 1 kayıt (commit)
  4. 07 Mar, 2019 1 kayıt (commit)
  5. 10 Eki, 2018 1 kayıt (commit)
  6. 09 Eki, 2018 1 kayıt (commit)
  7. 17 Eyl, 2018 1 kayıt (commit)
    • Stephan Bergmann's avatar
      New loplugin:external · 206b5b26
      Stephan Bergmann yazdı
      ...warning about (for now only) functions and variables with external linkage
      that likely don't need it.
      
      The problems with moving entities into unnamed namespacs and breaking ADL
      (as alluded to in comments in compilerplugins/clang/external.cxx) are
      illustrated by the fact that while
      
        struct S1 { int f() { return 0; } };
        int f(S1 s) { return s.f(); }
        namespace N {
          struct S2: S1 { int f() { return 1; } };
          int f(S2 s) { return s.f(); }
        }
        int main() { return f(N::S2()); }
      
      returns 1, both moving just the struct S2 into an nunnamed namespace,
      
        struct S1 { int f() { return 0; } };
        int f(S1 s) { return s.f(); }
        namespace N {
          namespace { struct S2: S1 { int f() { return 1; } }; }
          int f(S2 s) { return s.f(); }
        }
        int main() { return f(N::S2()); }
      
      as well as moving just the function f overload into an unnamed namespace,
      
        struct S1 { int f() { return 0; } };
        int f(S1 s) { return s.f(); }
        namespace N {
          struct S2: S1 { int f() { return 1; } };
          namespace { int f(S2 s) { return s.f(); } }
        }
        int main() { return f(N::S2()); }
      
      would each change the program to return 0 instead.
      
      Change-Id: I4d09f7ac5e8f9bcd6e6bde4712608444b642265c
      Reviewed-on: https://gerrit.libreoffice.org/60539
      Tested-by: Jenkins
      Reviewed-by: 's avatarStephan Bergmann <sbergman@redhat.com>
      206b5b26
  8. 29 Agu, 2018 1 kayıt (commit)
  9. 26 Agu, 2018 1 kayıt (commit)
  10. 30 Tem, 2018 1 kayıt (commit)
    • Gabor Kelemen's avatar
      Add missing sal/log.hxx headers · bdb0775a
      Gabor Kelemen yazdı
      rtl/string.hxx and rtl/ustring.hxx both unnecessarily #include <sal/log.hxx> (and don't make use of it themselves), but many other files happen to depend on it.
      This is a continuation of commit 6ff2d84a to be able to remove those unneeded includes.
      
      This commit adds missing headers to every file found by:
      grep -FwL sal/log.hxx $(git grep -Elw 'SAL_INFO|SAL_INFO_IF|SAL_WARN|SAL_WARN_IF|SAL_DETAIL_LOG_STREAM|SAL_WHERE|SAL_STREAM|SAL_DEBUG')
      to directories from filter to jvmfwk
      
      Change-Id: I2a73d63f2aaef5f26d7d08957daaa8a30b412ac5
      Reviewed-on: https://gerrit.libreoffice.org/58204
      Tested-by: Jenkins
      Reviewed-by: 's avatarMiklos Vajna <vmiklos@collabora.co.uk>
      bdb0775a
  11. 23 Tem, 2018 1 kayıt (commit)
  12. 18 Tem, 2018 1 kayıt (commit)
  13. 16 Nis, 2018 1 kayıt (commit)
  14. 11 Ara, 2017 1 kayıt (commit)
  15. 23 Eki, 2017 1 kayıt (commit)
  16. 04 Eki, 2017 1 kayıt (commit)
  17. 13 Eyl, 2017 1 kayıt (commit)
  18. 02 Eyl, 2017 1 kayıt (commit)
  19. 23 Haz, 2017 1 kayıt (commit)
  20. 12 Haz, 2017 1 kayıt (commit)
  21. 09 May, 2017 1 kayıt (commit)
  22. 07 May, 2017 1 kayıt (commit)
  23. 06 May, 2017 1 kayıt (commit)
  24. 21 Nis, 2017 1 kayıt (commit)
  25. 25 Mar, 2017 1 kayıt (commit)
  26. 31 Ock, 2017 1 kayıt (commit)
  27. 26 Ock, 2017 1 kayıt (commit)
    • Stephan Bergmann's avatar
      Remove dynamic exception specifications · e57ca028
      Stephan Bergmann yazdı
      ...(for now, from LIBO_INTERNAL_CODE only).  See the mail thread starting at
      <https://lists.freedesktop.org/archives/libreoffice/2017-January/076665.html>
      "Dynamic Exception Specifications" for details.
      
      Most changes have been done automatically by the rewriting loplugin:dynexcspec
      (after enabling the rewriting mode, to be committed shortly).  The way it only
      removes exception specs from declarations if it also sees a definition, it
      identified some dead declarations-w/o-definitions (that have been removed
      manually) and some cases where a definition appeared in multiple include files
      (which have also been cleaned up manually).  There's also been cases of macro
      paramters (that were used to abstract over exception specs) that have become
      unused now (and been removed).
      
      Furthermore, some code needed to be cleaned up manually
      (avmedia/source/quicktime/ and connectivity/source/drivers/kab/), as I had no
      configurations available that would actually build that code.  Missing @throws
      documentation has not been applied in such manual clean-up.
      
      Change-Id: I3408691256c9b0c12bc5332de976743626e13960
      Reviewed-on: https://gerrit.libreoffice.org/33574Tested-by: 's avatarJenkins <ci@libreoffice.org>
      Reviewed-by: 's avatarStephan Bergmann <sbergman@redhat.com>
      e57ca028
  28. 17 Ock, 2017 1 kayıt (commit)
  29. 13 Ara, 2016 1 kayıt (commit)
  30. 17 Şub, 2016 1 kayıt (commit)
  31. 08 Şub, 2016 1 kayıt (commit)
  32. 04 Şub, 2016 1 kayıt (commit)
  33. 30 Ara, 2015 1 kayıt (commit)
  34. 21 Ara, 2015 2 kayıt (commit)
  35. 20 Ara, 2015 1 kayıt (commit)
  36. 18 Ara, 2015 1 kayıt (commit)
  37. 03 Ara, 2015 1 kayıt (commit)
    • David Ostrovsky's avatar
      Add build toolchain to upload LibreOffice API to Maven Central · 1fd41f43
      David Ostrovsky yazdı
      Set up the toolchain to create sources and javadocs artifacts in
      addition to JARs created during the build. Use Buck build tool for
      that: [1]. This is a fork of Google's build tool Blaze, created by
      Xooglers at Facebook. This build tool (like Blaze itself) uses
      Python to write build files.
      
      Add needed tools and build files to install LibreOffice API artifacts
      to local Maven repository or deploy them to Maven Central.
      
      To build all needed artifacts LibreOffice must be built regularly
      with GNU make first. To build the rest of the API (sources and
      javadocs):
      
        $> buck build api
      
      To replace version number with upcoming release version:
      
        $> solenv/bin/version.py 5.1.0
      
      To install the API to local Maven repository:
      
        $> buck build api_install
      
      To deploy the API to Maven Central:
      
        $> buck build api_deploy
      
      Detailed documentation is added to document the prerequisites and
      the workflow to upload LibreOffice API to Maven Central.
      
      * [1] https://buckbuild.com
      
      Change-Id: Ibdd552a01110836703bc069abe829b9921491cac
      Reviewed-on: https://gerrit.libreoffice.org/20343Reviewed-by: 's avatarThorsten Behrens <Thorsten.Behrens@CIB.de>
      Tested-by: 's avatarThorsten Behrens <Thorsten.Behrens@CIB.de>
      1fd41f43
  38. 01 Ara, 2015 1 kayıt (commit)