You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2013/11/06 22:34:18 UTC
[jira] [Resolved] (TS-2108) TsConfig doesn't build with bison 3.0
[ https://issues.apache.org/jira/browse/TS-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan M. Carroll resolved TS-2108.
---------------------------------
Resolution: Fixed
Fix Version/s: (was: 4.2.0)
4.1.0
> TsConfig doesn't build with bison 3.0
> -------------------------------------
>
> Key: TS-2108
> URL: https://issues.apache.org/jira/browse/TS-2108
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: James Peach
> Assignee: Alan M. Carroll
> Fix For: 4.1.0
>
>
> With bison 3.0, the generated code has changes such that BisonHeaderToC.sed no longer edits the generated header correctly.
> TsConfigGrammar ends up looking like this:
> {code}
> namespace ts { namespace config {
> enum TokenType {
> {
> STRING = 258,
> IDENT = 259,
> INTEGER = 260,
> LIST_OPEN = 261,
> LIST_CLOSE = 262,
> GROUP_OPEN = 263,
> GROUP_CLOSE = 264,
> PATH_OPEN = 265,
> PATH_CLOSE = 266,
> PATH_SEPARATOR = 267,
> SEPARATOR = 268,
> ASSIGN = 269
> };
> }} // namespace ts::config
> {code}
> Maybe a more robust solution would be to include the generated header into another file that does the namespace.
--
This message was sent by Atlassian JIRA
(v6.1#6144)