Jens-G opened a new pull request, #2658:
URL: https://github.com/apache/thrift/pull/2658
Patch: Jens Geyer
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
[
https://issues.apache.org/jira/browse/THRIFT-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602785#comment-17602785
]
Jens Geyer commented on THRIFT-5626:
Testcase is struct Thrift5626 in NameConflictTest.thrift
>
[
https://issues.apache.org/jira/browse/THRIFT-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer updated THRIFT-5627:
---
Description:
As a side effect on my current work I recognized an interesting parser warning.
[
https://issues.apache.org/jira/browse/THRIFT-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer updated THRIFT-5627:
---
Description:
As a side effect on my current work I recognized a warning that was there
before:
[
https://issues.apache.org/jira/browse/THRIFT-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602770#comment-17602770
]
Jens Geyer commented on THRIFT-5627:
Ping [~codesf]
> More consistent syntax for cpp_type
>
Jens Geyer created THRIFT-5627:
--
Summary: More consistent syntax for cpp_type
Key: THRIFT-5627
URL: https://issues.apache.org/jira/browse/THRIFT-5627
Project: Thrift
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/THRIFT-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602765#comment-17602765
]
Jens Geyer commented on THRIFT-5626:
No
> Parser should not confuse data types and field names
>
yawaramin opened a new pull request, #2657:
URL: https://github.com/apache/thrift/pull/2657
My previous PR #2652 actually inadvertently broke the OCaml code generation
of class names. This is a follow-up to fix both that as well as the actual
issue of the exception constructor names, as
[
https://issues.apache.org/jira/browse/THRIFT-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602745#comment-17602745
]
Triton Circonflexe commented on THRIFT-5626:
For those interested in updating their own
> I’m not sure how to it works with Flex & Bison
Yes. If it would not, its the wrong tool.
See also https://issues.apache.org/jira/browse/THRIFT-5626 I'm on it
already.
Am 10.09.2022 um 11:16 schrieb Triton Circonflexe:
I’m not sure how to it works with Flex & Bison but there should be a
I’m not sure how to it works with Flex & Bison but there should be a way to
indicate that if the word in context should not be a specific token (in
this case, it’s not reserved), then the parser should fallback to interpret
it as something else (in this case, an identifier).
At the moment, every
emmenlau merged PR #2630:
URL: https://github.com/apache/thrift/pull/2630
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
emmenlau merged PR #2654:
URL: https://github.com/apache/thrift/pull/2654
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
Dear All,
I've just seen two Java-related issues in the Travis tests.
The first issue is that the build is killed after excessive logging
of warnings or errors. Probably, the true problem are the actually
logged errors, but I did not go any deeper :-) It shows here:
14 matches
Mail list logo