The curious pattern of pre-emptively rejecting the solution to your problem

re: The curious pattern of pre-emptively rejecting the solution to your problem

configurator — Thu, 07 Feb 2013 15:22:38 GMT

[It's essential if you want to avoid trailing spaces and don't want to run into trouble with lines that end in a digit. -Raymond]

Good point. I usually use bash where the trailing spaces are omitted unless quoted, so I wasn't aware of this problem.

re: The curious pattern of pre-emptively rejecting the solution to your problem

JamesJohnston — Thu, 07 Feb 2013 15:07:40 GMT

If the calling language doesn't "support" COM, what's so hard about using the vtable directly? After all, COM was explicitly designed to be usable from C and not require C++.

Writing a wrapper DLL and creating a whole new project might be a bit overkill...

re: The curious pattern of pre-emptively rejecting the solution to your problem

Douglas — Thu, 07 Feb 2013 14:01:23 GMT

@TightA***: Yes, the C# command-line compiler is installed with every version of the .NET framework. You do not need Visual Studio to build .NET applications.

re: The curious pattern of pre-emptively rejecting the solution to your problem

Damien — Thu, 07 Feb 2013 08:03:38 GMT

@Rick C - I was trying to highlight the users who *refuse* to tell you why. I admit, I've usually given up after only a single round or two.

re: The curious pattern of pre-emptively rejecting the solution to your problem

Drak — Thu, 07 Feb 2013 06:29:24 GMT

@TightA***: seeing as .NET websites that aren't precompiled use this compiler to compile on the fly as a page is served for the first time, I'd say that you have a good chance to find this compiler in the .NET framework folder :)

re: The curious pattern of pre-emptively rejecting the solution to your problem

voodoo42 — Thu, 07 Feb 2013 06:25:19 GMT

@Chris Chiesa: So we have you to thank for all those horrible GUIs that ignore all conventions and user defined properties? Believe me you may think that having 50 applications on your desktop that all look and behave completely different from each other is great, but users disagree.

re: The curious pattern of pre-emptively rejecting the solution to your problem

TightA*** — Thu, 07 Feb 2013 02:16:50 GMT

"%windir%\Microsoft.NET\Framework\v4.0.30319\csc changeColor.cs"?

Is this suggesting that the C# command line compiler comes with the .NET framework? Can we therefore use it without Visual Studio? Not that it probably matters since VS Express is free anyway but this would be a way to use it without installation of the VS product.

re: The curious pattern of pre-emptively rejecting the solution to your problem

Chris Chiesa — Thu, 07 Feb 2013 02:16:10 GMT

I might want the SetColor equivalent that works on all controls, not just those the Microsoft API designers decided to permit. What's the big damn deal about letting me make e.g. a "STOP!" button that's red with white lettering even though the system Button Face Color is part of the systemwide theme / colorscheme? I frequently have reasons to want to get around ARTIFICIAL LIMITATIONS in the abstract APIs that have been wrapped around the fundamentals that do what I want.

re: The curious pattern of pre-emptively rejecting the solution to your problem

Joshua — Wed, 06 Feb 2013 23:22:09 GMT

@Matteo: Because the static CRT isn't redistributable (as in the .LIB file, not the resulting binary).

re: The curious pattern of pre-emptively rejecting the solution to your problem

Matteo Italia — Wed, 06 Feb 2013 21:38:47 GMT

@Joshua: I don't see the problem, why can't you just statically link the CRT? It's routinely done for small utilities and other situations when you don't want to have the CRT package as a dependency.