I feel so dirty
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
Gary Wheeler wrote:
I just coded used #define in a C# application for the first time.
FFY. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles] -
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
I've been teaching VB for weeks. X|
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
Gary Wheeler wrote:
I feel so dirty
Panic, Chaos, Destruction. My work here is done. or "Drink. Get drunk. Fall over." - P O'H
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
You must be carrying your C/CPP habbit!! That happens :)
Thanks, Arindam D Tewary
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
I do that all the time when I'm testing alternatives to prior code blocks. That way, I can always revert back to what was working if things go completely sideways on me.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
Gary Wheeler wrote:
I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.
Isn't this what source control is for? :confused:
3x12=36 2x12=24 1x12=12 0x12=18
-
Gary Wheeler wrote:
I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.
Isn't this what source control is for? :confused:
3x12=36 2x12=24 1x12=12 0x12=18
No, because other parts of this piece of code are evolving. I'm using the
#define
to preserve the original behavior, while allowing me to update the rest of the class. If this was a change in a single location, I would just comment-out the code and be done with it. Unfortunately, it requires a change in several places, so the#define
was the better solution.Software Zen:
delete this;
-
Gary Wheeler wrote:
I just coded used #define in a C# application for the first time.
FFY. :)
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]Actually not. I've been developing in C# for two years now.
Software Zen:
delete this;
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
I just love littering my code base with:
Console.Writeline(
#if DEBUG
"Foo"
#else
"Bar"
#endif
); -
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
Welcome to the dark side.
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
I don't see what the problem with that might be, as long as it isn't over done. I use it all the time to keep the source code for my Commercial, Demo and Student versions organized.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
I just used
#define
in a C# application for the first time :-O. I've been told to change a feature that I'm reasonably certain will revert to the original behavior before release, so this lets me switch easily. Sigh.Software Zen:
delete this;
If it's code that can be tossed into a few methods, I like this type of solution.
-
If it's code that can be tossed into a few methods, I like this type of solution.
Very interesting; thanks for the link!
Software Zen:
delete this;