|
Oh, great, now I have an opening for something I was thinking yesterday:
A song that was playing used the phrase, "the wrong end of a gun".
Does the anti-gun crew consider both ends of a gun to be "wrong"? 
|
|
|
|
|
Too bad 'free()' wasn't defined as returning a (void *). In that case, the code could have been written as:
flag = free(flag);
In case of any error other than a null pointer being passed in, free() could return the passed-in pointer.
Similar behavior could have been used with fclose() [return a (FILE*)] and other such functions that destroy the object whose pointer is passed to them. Oh well, only a few decades too late now.... Where's my time machine?
|
|
|
|
|
Discovered this gem in our code base (C#, but I guess that won't make much difference)...
if (transparent)
pdfDoc.HtmlOptions.HideBackground = true;
pdfDoc.HtmlOptions.HideBackground = true;
Rob
|
|
|
|
|
Well, if opaque then it's true, on the other hand, if transparent then it's so true.
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
|
|
|
|
|
I remember having to do something like that; repainting a dynamic form I think. It was easier to do the repaint twice based on a simple condition then to code a nasty, recursive, snaking, 683 if level method.
But I put a comment in to explain why.
Panic, Chaos, Destruction.
My work here is done.
|
|
|
|
|
No, nothing like that. Fortunately, we have a great Refactoring policy here that allowed me to simply fix the code. All is working fine, so I guess it was... well actually I've no idea. 
|
|
|
|
|
re-wording a famous Shakespare quote:
To hide, or not to hide...
|
|
|
|
|
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
“The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson
|
|
|
|
|
Boss Type: ... Hmmm, do you think this will be a problem?
VB6'er*: Well, the thing is there's no way to get the ID of the rows you've just updated in SQL Server.
[Much later]
VB6'er: The input data must have been invalid - and then the import failed part way through updating twenty odd tables, but I don't know where. This is going to take me hours to sort out!
Boss Type: Well we need this sorted asap! I don't care if you have to work 'til midnight!
Cleaning Lady** [passing by, busy hoovering]: Sounds to me like you should have used a transaction...
[Exeunt stage left martin_hughes, chortling]
* I assume he is, he looks like one, at any rate.
** Added under poetic licence for comedy reasons.
|
|
|
|
|
martin_hughes wrote: * I assume he is, he looks like one, at any rate.
I'm curious, what does a VB6er look like these days?
I'm largely language agnostic
After a while they all bug me 
|
|
|
|
|
|
That would be a South Asian analogue to Junior Samples[^], mayhap?
"Friends don't let friends write VB6" -- Tech Sage
"Friends don't let friends manage VB6 projects" -- Experienced Manager Sage
|
|
|
|
|
MidwestLimey wrote: I'm curious, what does a VB6er look like these days?
Yesterday it was cheanos and a rugby shirt, but today I'm wearing a rather fetching olive (coloured) suit.
Panic, Chaos, Destruction.
My work here is done.
|
|
|
|
|
My mirror says: Khaki shorts (with blindingly white legs sticking out of them), black T-shirt, a mostly gray absence of a haircut and glasses that were in fashion ten years ago or so...
Admittedly, I do a lot of C# these days and I come from a C background, but I do a lot of maintenance on my old VB6 code and even more VBScript. Not that I want to, but you know, there are these little creatures called customers that you sometimes have to take into account...
Later,
--
Peter
|
|
|
|
|
MidwestLimey wrote: I'm curious, what does a VB6er look like these days?
Normal... until the sun goes down...
The VB'ers then sprout large fangs, and multiple "insect like" legs. They then roam the streets looking for innocent software to devour.... ATM's, Petrol pumps, desktop PC's... nothing is safe...
|
|
|
|
|
Is nowhere safe!?
|
|
|
|
|
AEternal wrote: Is nowhere safe!?
I normaly hide in element 0 of an array. VB6er tend not to look there... 
Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all.
Douglas Adams, "Dirk Gently's Holistic Detective Agency"
|
|
|
|
|
martin_hughes wrote: ** Added under poetic licence for comedy reasons.
roffle
|
|
|
|
|
Do you guys all work at M$?
|
|
|
|
|
What was I thinking?
private static ProtoBlock LoadBlock(int x, int y, ByteReader stream, BlockHolder[,] blocks)
{
if (stream == null)
return RadishHelper.LoadBlockData(x, y, blocks, null);
return RadishHelper.LoadBlockData(x, y, blocks, stream);
}
Firstly, there is no need to check for null, as it is quite possible to pass null values on if it is a null.
Secondly, since the first point is true, this method only calls the other method, with no logic whatsoever.
|
|
|
|
|
Oh, it's simply self-encouraging code.
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
|
|
|
|
|
jamie550 wrote: What was I thinking?
About how sweet it will be when you finish up, and can go have a beer at the pub perhaps? 
|
|
|
|
|
Well, there is this curious item: BlockHolder[,]
|
|
|
|
|
That is one of the 2 ways to declare a multi-array, the other way is [][]
|
|
|
|
|
I believe there's a difference:
int x[][] will declare an array of arrays of integers, each of which may be initialised with its own number of elements (i.e. a jagged array).
int x[,] declares a 2-dimensional array, where the bounds of each dimension are specified when created and fixed.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
