Quick C# quiz

honey the codewitch

foo("bar");

does this refer to an invocation of the method foo? or an invocation of the delegate instance referred to by the variable or argument foo? *headdesk* C# is massively ambiguous without having type information, so now I get to write a visitor to "patch up" the code dom with type information. So basically i always create these expressions as delegate invocations, but then i have to go back through later and find types, so I can change the right ones to method invocations instead. I know C family languages require type information to parse (which is unfortunate) but C# takes it to another level. In for a penny, in for a pound I guess.

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.

OriginalGriff

honey the codewitch wrote:

does this refer to an invocation of the method foo? or an invocation of the delegate instance referred to by the variable or argument foo?

Neither: it means a VB programmer wants to access an array element and forgot where he was.

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!

honey the codewitch

lol, i'm glad my c# compiler doesn't see it that way. =)

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.

Richard Deeming

honey the codewitch wrote:

does this refer to an invocation of the method foo? or an invocation of the delegate instance referred to by the variable or argument foo?

Yes. :)

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

honey the codewitch

you get an A and i get a headache

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.

PIEBALDconsult

# define foo(x) this.GoToThe(x)

OriginalGriff

Well, you can't say I never give you anything useful[^] :-D

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!

Richard Deeming

Thankfully that doesn't work in C#. :) #define - C# Reference | Microsoft Docs[^]

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

OriginalGriff

Nor does

#define if while

:-D

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony AntiTwitter: @DalekDave is now a follower!

Lost User

#define then { #define endif } lets make C really basic so anyone can do it Edit: more complete #define IF if ( #define THEN ) { #define ELSE } else { #define ENDIF }

this internet has become nothing but fake news. ... time to fix it, time to get back to the fax!

PIEBALDconsult

The C pre-processor works just fine with C# code.

BillWoodruff

PIEBALDconsult wrote:

The C pre-processor works just fine with C# code.

That's very interesting; please say more.

«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali

enhzflep

I wonder if the fact that the notion of successfully creating useful output isn't mentioned, is relevant? I'm sure it would be perfectly happy to tell you whereabouts the input file contained text that wasn't C compliant. In that case, I'd say that it did in fact work just fine with what you gave it. That you gave it C# when it has a dietary restriction that only allows it to consume C is irrelevant. The pre-processor still ran and exited without an error code, a crash or undefined behaviour. Reasonable people call them Semantics, others think that Symantec's is about tiny differences in language, rather than a word that implies ownership by the Symantec company.. Going to be interesting to see what the answer is on this one. :)

Sander Rossel

honey the codewitch wrote:

does this refer to an invocation of the method foo? or an invocation of the delegate instance referred to by the variable or argument foo?

It's the latter which I know because of casing. If it were the former surely it would be Foo("bar"); :D Oh, but I forgot, style isn't important and we can forget about consistency. We write for compilers and they can read it just fine :doh:

Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly

honey the codewitch

do you REALLY want me to enforce title casing for methods vs fields? because I can do that, and it makes my job a HELL of a lot easier.

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

"Everything is exactly as useful as you make it." - Hacker lore "Everything is exactly as real as it is useful." - Honey the Monster. :cool:

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

I've killed for less

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

I was thinking of this conversation of a while back: The Lounge[^] Unfortunately, not everyone agreed with me and so they were wrong ;) I won't mention names (although it's quite easy to look up), but someone literally said "Style is not important because you're writing code for compiler to read, not for developers." And here you are wondering what the hell you're looking at while I would be absolutely sure (in my own code) because I CARE ABOUT STYLE! :cool: I wouldn't mind enforcing PascalCase for methods and camelCase for fields and variables :)

Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly

honey the codewitch

I agree with SuperLloyd in that discussion. Context is everything.

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

Message analysis complete. Found 1 error in "I agree with SuperLloyd" on line 1 column 0. Suggested fix: change "SuperLloyd" to "Sander". Compilation failed.

Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly