[Bug c++/99558] wrong argument types reported for "no matching function" error message if ctor argument is a variable

2021-03-12 Thread jfhart085 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99558 --- Comment #2 from J. Hart --- Thank you very much for your kind attention and assistance. I had thought it was indicating a reference rather than an lvalue. Your correction is most useful and appreciated. I deliberately introduced the sec

[Bug c++/99558] New: wrong argument types reported for "no matching function" error message if ctor argument is a variable

2021-03-12 Thread jfhart085 at gmail dot com via Gcc-bugs
Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jfhart085 at gmail dot com Target Milestone: --- Created attachment 50371 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=5037

[Bug c/77410] macro reference supplied as macro reference argument is not expanded

2016-08-29 Thread jfhart085 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77410 --- Comment #1 from J. Hart --- If an additional level of macro referencing is added, the result is correct. It would appear that if an argument is directly used with an concatenation directive, that argument is not expanded. example: #define M