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

Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/12/16 01:46:14 UTC

[jira] [Commented] (TS-1256) Streamline usage of PATH_NAME_MAX

    [ https://issues.apache.org/jira/browse/TS-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247511#comment-14247511 ] 

ASF subversion and git services commented on TS-1256:
-----------------------------------------------------

Commit f2fc289026553b57461dc2a5395aefce842839c1 in trafficserver's branch refs/heads/master from [~jpeach@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f2fc289 ]

TS-1256: add ink_file_namemax to replace raw pathconf calls


> Streamline usage of PATH_NAME_MAX
> ---------------------------------
>
>                 Key: TS-1256
>                 URL: https://issues.apache.org/jira/browse/TS-1256
>             Project: Traffic Server
>          Issue Type: Task
>          Components: Cleanup
>            Reporter: Igor Galić
>            Assignee: James Peach
>              Labels: newbie
>             Fix For: 5.3.0
>
>
> There are right now two different usages of the constant {{PATH_NAME_MAX}} in variable declarations:
> {code}
> char foo[PATH_NAME_MAX];
> {code}
> and
> {code}
> char bar[PATH_NAME_MAX + 1];
> {code}
> Since we define what {{PATH_NAME_MAX}} is ourselves, we should streamline our code to only use the first kind of declaration.



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