You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2016/08/16 17:29:21 UTC

[jira] [Closed] (TS-2851) Cleanup iobuffer "index" types

     [ https://issues.apache.org/jira/browse/TS-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Call closed TS-2851.
--------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: sometime)

> Cleanup iobuffer "index" types
> ------------------------------
>
>                 Key: TS-2851
>                 URL: https://issues.apache.org/jira/browse/TS-2851
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Leif Hedstrom
>
> Unfortunately (my bad...) we use int64_t's for various index types / parameters for iobuffers. This makes no sense, in some cases, it ought to just be unsigned, or size_t or some such.
> The wrinkle here is that (if I recall) that sometimes we overload parameters to mean both indexes (0, 1, 2 etc.) or sizes (if negative). In those cases, if we retain that overloading, we need them to be int64_t's.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)