[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-c-dev
Subject:    [jira] [Closed] (AXIS2C-1698) Investigate inner workings of guththila_token_list_*
From:       "Bill Blough (JIRA)" <jira () apache ! org>
Date:       2019-01-29 20:18:00
Message-ID: JIRA.13159911.1526526040000.197575.1548793080265 () Atlassian ! JIRA
[Download RAW message or body]


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

Bill Blough closed AXIS2C-1698.
-------------------------------
    Resolution: Not A Problem

> Investigate inner workings of guththila_token_list_*
> ----------------------------------------------------
> 
> Key: AXIS2C-1698
> URL: https://issues.apache.org/jira/browse/AXIS2C-1698
> Project: Axis2-C
> Issue Type: Task
> Components: guththila
> Reporter: Bill Blough
> Priority: Minor
> 
> While implementing additional tests for guththila, I noticed that \
> guththila_token_list_init and guththila_token_list_grow allocate memory that does \
> not appear to be used, with the exception of pushing addresses of empty elements \
> onto the token stack.   Since the functions to get/set tokens in the list directly \
> call pop/push on the stack, it seems to me that the additional allocations are \
> unnecessary.   However, since I'm still getting familiar with the codebase, I don't \
> want to make major changes based on assumptions. This task is a reminder to go back \
> and investigate whether these allocations are truly necessary, and if not, \
> eliminate them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]