|
SPIDERZZ!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I'm afraid of FEAR
a few SOME
but I'm scary
FEARSOME
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yep too late though
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
|
|
|
|
|
So there are actually two answers?
|
|
|
|
|
So you make me hero or zero ?
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
This is what happens when people take too long to answer... OP forgets what the actual answer is
|
|
|
|
|
You're not wrong
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
|
|
|
|
|
Erm ... FEARLESS doesn't mean "scary" ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
for me it does
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
Well who's up tomorrow?
You? Your answer is correct!
I have 2 CCC's ready, but you might have that too
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
No, you can take it if you want it - not a problem for me!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
pkfox has just replied and says it's me - but I'm happy for you or me to do it.
Do you want it? Say the word and it's yours!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
You won, you do it tomorrow. I'll compete again
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
Sorry griff see my apology - you are up tomorrow
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
|
|
|
|
|
getEnum.Statements.Add(
new CodeMethodReturnStatement(
new CodeObjectCreateExpression(
"TableTokenizerEnumerator",
new CodeMethodInvokeExpression(
new CodeMethodReferenceExpression(
new CodeFieldReferenceExpression(
new CodeThisReferenceExpression(),
innerField.Name),
"GetEnumerator")),
new CodeFieldReferenceExpression(new CodeThisReferenceExpression(), dfaTableField.Name),
new CodeFieldReferenceExpression(new CodeThisReferenceExpression(), blockEndsField.Name),
new CodeFieldReferenceExpression(new CodeThisReferenceExpression(), nodeFlagsField.Name))));
All that, to make this:
return new TableTokenizerEnumerator(this._inner.GetEnumerator(), this._dfaTable, this._blockEnds, this._nodeFlags);
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I don't always use Expression Trees, but when I do it's a big, long, unreadable Christmas tree
I usually try to first declare all kinds of Expressions in variables and then use those, but it's usually a lost cause.
|
|
|
|
|
at one point I went as far as creating a limited programming language that resolved to code dom constructs instead of code. i called it slang and it could emit VB, C# or whatever. Unfortunately it was proprietary as part of a company's IP i worked for at the time or I'd be using it now.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
I only need them when working with some generic EF code.
Only once did I need it to output code and that was for an article
|
|
|
|
|
Code generation is sort of specialized, but I've always written code to write code.
My father was a toolmaker - he used to make machines that stamped sheetmetal for parts for large trucks and stuff. Weird job, but I think I've got it in my blood, as I prefer to make tools for other people to make stuff with, and that involves codegen a lot. =)
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
|
LOL
You're gonna hate me, but none of my generated code ever has Finalize() methods unless it's only C# and not the codedom.
but lately all my generation code has used the codedom, just so I can support VB
to be honest i don't even know VB syntax.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
honey the codewitch wrote: You're gonna hate me, but none of my generated code ever has Finalize() methods Why would I hate you for that?
I've never written a finalizer in my life... Or thinking back on it, once, maybe.
honey the codewitch wrote: to be honest i don't even know VB syntax. To tell you an uglier truth, I do
|
|
|
|
|
I know VB6 and VBScript pretty well as a matter of necessity in the bad old days of microsoft land when every idiot fine programmer out there was using it to write bad software. It was usually my job to try and fix it, which really meant gleaning the functional requirements from undocumented source code and then rewriting.
Since .NET i've seen little of it, and I've had no use for VB.NET.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
Sander Rossel wrote: To tell you an uglier truth, I do
And what's the problem with that?
Are you becoming a snob as well?
|
|
|
|
|
Jörgen Andersson wrote: And what's the problem with that? You wouldn't be asking me this is you saw the VB code I had to work with
I used to love VB.NET, even after I started doing C#.
But after years of doing C# I now have to use it again and it's just lagging behind in pretty much everything.
The fact that Option Strict is off by default (causing much of my current problems) makes it bad by default.
Sub and Function As Object (or worse, just Function without an As clause because that's optional without Option Strict) feels weird.
The default indentation in Visual Studio sucks.
If something AndAlso
somethingElse Then
DoSomething()
ThisIsAlsoAFunction
End If Keywords like End Function , AndAlso and OrElse are unnecessarily long.
Don't even get me started on lambda's! collection.Where(Function(x) x.Something) vs. collection.Where(x => x.Something) !
Meanwhile, shortcuts like inline ref variables don't make it to VB.
Because it's not case sensitive myVar and MyVar are the same, meaning I sometimes need to think just a bit harder to name my variables.
Static classes don't exist, you need a Module , but that's slightly different (in that functions become public without the need of using the class name) making a Private Class with Private Sub New() the closest to a static class.
And please don't use the default VB namespace Modules that are imported by default!
If I'm honest, I've never seen good VB code that I didn't write myself, while I've seen some good C# code.
Microsoft is quickly dropping support for new platforms and VB.
It's only just been added to .NET Core with version 3, together with WinForms support.
Try finding (good) code samples for VB online.
Even newer Visual Studio functionality, like code cleanup, is not available for VB.
All in all, I have no reason whatsoever (or even a choice) to use VB in any modern software development.
Let me end with a small positive note for the language I started in.
One thing VB does right (in WinForms development) is Sub MyButton_Click(sender As Object, e As EventArgs) Handles MyButton.Click , which I find more clear than the C# way of adding a handler in the designer.
|
|
|
|