Come on Microsoft!
-
Update: It was my fault and I feel like an idiot. I went over my code with a fine tooth comb before posting this, and I could have sworn it wasn't me. It was, and I just somehow missed it. My fault. :rolleyes: Microsoft has this tech called the CodeDOM that is an object model for an abstract syntax tree representing generic code independent of language. It can render the trees to C#, VB.NET or another .NET language like perhaps IronPython or whatever - anything that can be used with ASP.NET, because that's where Microsoft employs this tech. It's ancient code and should be battle tested at this point. I found a bug with their VB code renderer:
''' Reference implementation for generated shared code
'''
'''This is how doc comments end up when declared on a type. Everywhere else they are fine. Only on the type declarations are they messed up. But because of that, Rolex generates incorrect VB doc comments, and there's little I can do about it, because it's not my code that is broken. I might be able to do a workaround but it pains me to even think about given what it requires.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Update: It was my fault and I feel like an idiot. I went over my code with a fine tooth comb before posting this, and I could have sworn it wasn't me. It was, and I just somehow missed it. My fault. :rolleyes: Microsoft has this tech called the CodeDOM that is an object model for an abstract syntax tree representing generic code independent of language. It can render the trees to C#, VB.NET or another .NET language like perhaps IronPython or whatever - anything that can be used with ASP.NET, because that's where Microsoft employs this tech. It's ancient code and should be battle tested at this point. I found a bug with their VB code renderer:
''' Reference implementation for generated shared code
'''
'''This is how doc comments end up when declared on a type. Everywhere else they are fine. Only on the type declarations are they messed up. But because of that, Rolex generates incorrect VB doc comments, and there's little I can do about it, because it's not my code that is broken. I might be able to do a workaround but it pains me to even think about given what it requires.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Oh well, even Homer nods. :-\
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
Update: It was my fault and I feel like an idiot. I went over my code with a fine tooth comb before posting this, and I could have sworn it wasn't me. It was, and I just somehow missed it. My fault. :rolleyes: Microsoft has this tech called the CodeDOM that is an object model for an abstract syntax tree representing generic code independent of language. It can render the trees to C#, VB.NET or another .NET language like perhaps IronPython or whatever - anything that can be used with ASP.NET, because that's where Microsoft employs this tech. It's ancient code and should be battle tested at this point. I found a bug with their VB code renderer:
''' Reference implementation for generated shared code
'''
'''This is how doc comments end up when declared on a type. Everywhere else they are fine. Only on the type declarations are they messed up. But because of that, Rolex generates incorrect VB doc comments, and there's little I can do about it, because it's not my code that is broken. I might be able to do a workaround but it pains me to even think about given what it requires.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
honey the codewitch wrote:
It's ancient code and should be battle tested at this point.
Err...facts not in evidence!
honey the codewitch wrote:
This is how doc comments end up when
With doc comments? That would of course be the least tested.
Well as per my edit, it turns out the problem was with my code. I don't assume other people's code is the problem until I feel I've exhausted the possibilities of it being my code. However, this time I missed it despite my efforts.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix