Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
vala
vala
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 701
    • Issues 701
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 39
    • Merge Requests 39
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • GNOME
  • valavala
  • Issues
  • #391

Closed
Open
Opened Jul 06, 2013 by bugzilla-migration@bugzilla-migrationReporter

Use the offsets for computing the private data offsets

Submitted by Emmanuele Bassi @ebassi

Link to original bug (#703705)

Description

GLib 2.38 changed the in-memory layout of instance and private data:

https://blogs.gnome.org/ebassi/2013/06/21/the-king-is-dead/

and introduces new API and macros to deal with this that make private data pointers obsolete.

Vala should switch to this new offset-based access, so that newly added API that relies on offsets (like the GTK template children API) can use it.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
1.0
Milestone
1.0
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/vala#391