The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Specialization: Removes circumvention ads in Adblock Plus
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
Of those, I use only SQL, and it's worse than that. (Transact-SQL at least.)
Remember that RTRIM and LTRIM remove only SPACEs, not all whitespace.
Basically, LEN (and RTRIM and LTRIM) work on bytes, so it does the same things with VARBINARY as it does with VARCHAR.
So I should not have been surprised when performing LEN on a VARBINARY ignores 0x32 at the end as well.
This is my fave thing to do in a query window for a quick update:
BEGINBEGINTRANUPDATE [SomeTable] SET [someColumn] = 'someNewValue'WHERE [someID] = 0ROLLBACKCOMMITEND
I still get intellisense within the BEING/END area and, should I accidentally press F5 or run the silly thing w/o selecting the code to run, no harm done.
Yeah, I know, gotta make sure I include the WHERE clause, and also BEGIN TRAN. I then select and run COMMIT.
The best way to improve Windows is run it on a Mac.
The best way to bring a Mac to its knees is to run Windows on it.
~ my brother Jeff
This is the kind of crap you get in a weakly typed language.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I had never thought about pointer arithmetic being commutative before... seems consistent at least.
int index = 1;
char *address = "String";
index[address] is the same as *(index + address)
address[index] is the same as *(address + index)
implicitly includes the size of the base data type. (char)
If this was attempted with variables instead of constants, you might end up with memory protection issues. Most OSes would not want you to start a loop by loading memory address 1 into a register.
They would let you load the memory address of "String"
I remember being frustrated by the fact C# 1.0 had a default container called ArrayList. Is it an Array, or a List? These are very different things. Is it a fancy container that somehow has worked out how to get the benefits of both? The documentation never said.