1. 27 Jun, 2018 1 commit
  2. 26 Jun, 2018 3 commits
  3. 23 Jun, 2018 1 commit
  4. 20 Jun, 2018 2 commits
  5. 19 Jun, 2018 2 commits
  6. 15 Jun, 2018 1 commit
  7. 13 Jun, 2018 5 commits
  8. 12 Jun, 2018 1 commit
  9. 10 Jun, 2018 4 commits
  10. 09 Jun, 2018 5 commits
  11. 08 Jun, 2018 2 commits
  12. 05 Jun, 2018 1 commit
  13. 03 Jun, 2018 2 commits
  14. 02 Jun, 2018 1 commit
    • Philip Chimento's avatar
      object: Warn about finalized GObject in fewer cases · 8cdd6291
      Philip Chimento authored
      We want to remove this warning in cases where the subsequent code isn't
      actually trying to access the underlying GObject and therefore isn't
      going to crash. On resolve() we don't want the warning, as that only
      applies to prototype objects. On trace() we don't want it either, as that
      may legitimately be called during the GC mark phase on a JS wrapper with
      a disposed GObject.
      
      In the typecheck function, we only use the GObject for a debug assertion.
      All the other checks use the GType. We relax the assertion and only do
      the debug sanity check if the GObject is still alive. Instead of logging
      the warning here, we log the warning in gjs_g_object_from_object() which
      happens later when the GObject is actually used.
      
      We keep the warnings in property getters and setters, since those would
      access the underlying GObject, and they are now only called for names
      that really do resolve to GObject properties and fields.
      
      Closes: #24
      8cdd6291
  15. 01 Jun, 2018 4 commits
  16. 31 May, 2018 5 commits