Closed GoogleCodeExporter closed 8 years ago
Hi Josh,
I'm not sure there is much we can do about the duplicate name issue. It is
likely an indicator of functions that have been wrongly assigned/matched and
for which we shouldn't be porting names in the first place. The only remedy is
working through the list of matched functions manually and confirming the
matches/porting symbols individually. I'll look into other solutions but I'm
not overly optimistic.
For the invalid characters issue: Are you dealing with C++ mangled names? Do
you have examples of function names where this happens?
best regards,
Sören
Original comment by soere...@google.com
on 27 Aug 2012 at 8:51
I do know that in the API (scripting, not modules) you can pass a value (when
you rename) which then gives you the "do not display again" error message.
Haven't developed a module in about 6 months but it should be there.
Original comment by ooto...@gmail.com
on 27 Aug 2012 at 1:26
Yes, but where that flag is applicable it will also be shown in the UI as a
checkbox for the user to select.
Original comment by soere...@google.com
on 27 Aug 2012 at 2:44
Isn't that good though? Then I can just check it and ignore future error
messages? Or do you mean I should have a setting somewhere I can check?
Original comment by ooto...@gmail.com
on 27 Aug 2012 at 2:45
No, I meant to say that I think the checkbox will be shown even now if it is
possible to ignore the error. Like you said in your original post - you did get
the option to ignore future warnings for some types of warning already.
Would you mind sending me the idbs in question so I can reproduce the issue and
see what I can do?
Original comment by soere...@google.com
on 27 Aug 2012 at 3:06
Absolutely - how do I grab your email?
Also, I have a function renaming script (not plugin) that you can change the
variable and it give you the checkbox. I'll send you that script as well.
Thanks!
Original comment by ooto...@gmail.com
on 27 Aug 2012 at 3:52
You should be able to attach files to this case which would be preferable to
email. I'm available as soerenme@google.com.
Original comment by soere...@google.com
on 28 Aug 2012 at 8:20
Original issue reported on code.google.com by
ooto...@gmail.com
on 26 Aug 2012 at 10:19Attachments: