Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • U uPython-mirror
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TASTE
  • uPython-mirror
  • Repository
Switch branch/tag
  • uPython-mirror
  • py
  • runtime.c
Find file BlameHistoryPermalink
  • Damien George's avatar
    py: For malloc and vstr functions, use size_t exclusively for int type. · b0261341
    Damien George authored Sep 23, 2014
    It seems most sensible to use size_t for measuring "number of bytes" in
    malloc and vstr functions (since that's what size_t is for).  We don't
    use mp_uint_t because malloc and vstr are not Micro Python specific.
    b0261341