Closed GoogleCodeExporter closed 9 years ago
Humbug. I suspect this is due to an indexer being called Item as well. Should
be fixable though - will take a look. It won't be in the next week though I'm
afraid, as I'm going to be away.
If anyone else wants to fix it, I suspect it's just a case of changing the call
to GetProperty to make sure we only match "true" properties, not indexers.
Original comment by jonathan.skeet
on 31 May 2012 at 7:09
Fixed in revision 132a1094a3c4, then merged in revision 69bf0fe9e8ee.
(Not in a distribution build yet.)
Original comment by jonathan.skeet
on 4 Jun 2012 at 9:54
is this fix available in latest revision(head)
Original comment by waghmare...@gmail.com
on 21 Oct 2013 at 1:42
Yes, as far as I can tell, it should be fine in head. Did you have problems?
Original comment by jonathan.skeet
on 21 Oct 2013 at 8:45
yeah, i am still getting the error mentioned in the original post, and i also
cant see the code changes latest revision 83bc9fb7fb05
Original comment by waghmare...@gmail.com
on 22 Oct 2013 at 6:30
its seems that it never got merged to main branch
132a1094a3c4 Fixed
69bf0fe9e8ee Merged
d2b41ee25a49 Merged
3c02ffab3fb8 Merged, and never got back to original branch
Original comment by waghmare...@gmail.com
on 22 Oct 2013 at 6:35
I'll have another look tomorrow night (I can't look tonight I'm afraid), but on
the default branch I can see the unit test for a message with a field called
"item", and the code which is in revision 132a1094a3c4 does seem to be merged
in...
Original comment by jonathan.skeet
on 22 Oct 2013 at 6:42
Nope, I can't reproduce this using the latest code. Steps I took:
- Define a message as per the top of this issue
- Build with just "protogen foo.proto"
- Create a test class:
class Test
{
static void Main()
{
var builder = new Foo.Builder();
}
}
- Compile with "csc Test.cs Foo.cs /r:Google.ProtocolBuffers.dll"
- Run test.exe
No exceptions. Please could you try these steps yourself? If they work but
you're still getting the problem in your real code, we need to look more
closely at what you're doing to reproduce the problem in a short example.
Original comment by jonathan.skeet
on 22 Oct 2013 at 7:01
Jon i have created a new issue, please see 69 for more details about how to
repro
Original comment by waghmare...@gmail.com
on 22 Oct 2013 at 7:04
Original issue reported on code.google.com by
brandon....@trms.com
on 31 May 2012 at 6:14