|
whoops - there's a lesson to be learnt there !
(don't get found out)
|
|
|
|
|
I didn't tell, the BFF did. 
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs Jim<</xml>
|
|
|
|
|
BFF's are thicker than water ?
um, I mean, ... nah, stuff it 
|
|
|
|
|
Yes, and she seduced me. 
On a positive note we were having a trial separation and after this disclosure I can say it worked. 
Once you lose your pride the rest is easy.
In the end, only three things matter: how much you loved, how gently you lived, and how gracefully you let go of things not meant for you. – Buddha
Simply Elegant Designs Jim<</xml>
|
|
|
|
|
She landed on her rear parts, then fell flat on her face and disappeared in a cloud of debris?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
|
|
|
|
|
Marc Clifton wrote: I must figure out where I can use that phrase somewhere else though!
Glasgow pub on a Saturday night?
"Ay you - shut your gob or you'll get a R. U. D.".
Second thoughts, no - I think not - the Glasgow kiss will prevail.
|
|
|
|
|
I've been looking at that video a couple of times now, and I don't believe they're telling the whole truth.
The rocket arrives at a fairly high lateral speed from seven o'clock, overshoots, overcompensates and topples over.
Maybe because of lack of hydraulic fluid as they claim, but I believe it might be simpler than that. They missed.
|
|
|
|
|
They ran out of hydraulic fluid while they were descending, which caused vehicle control to fail. It's rather amazing how close they came.
Think of it as writing 10,000 lines of code and getting only one compile error on your first build.
Software Zen: delete this;
|
|
|
|
|
Ran out of fluid.
That's the part I'm having a problem with.
All hydraulic systems I know about are closed systems, such as the brakes for a car, or the hydraulic pistons on an excavator.
If your car runs out of brake fluid you don't bring 50% more next time, as has been claimed, you fix the leak.
|
|
|
|
|
In worst case when I had to make a work around for third party libraries I did the following:
#define private public
No it is not dirty it is simply pragmatic 
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Take it to "Weird and wonderful".
P.S. -- "Dirty" would be defining it on the command line, in a batch file, or in a make file. 
|
|
|
|
|
Do you work for the government?
|
|
|
|
|
No not for government, for NSA
Ok in real it was #define private NSA
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Bruno Sprecher wrote: No it is not dirty it is simply pragmatic
Or is it creative programming?
Nah it's dirty!
New version: WinHeist Version 2.1.0
My goal in life is to have a psychiatric disorder named after me.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
|
|
|
|
|
Sales man says: It's creative
Programmer says: Nah it's dirty!
Me: pull the head / neck from the noose
Bruno
modified 19-Jan-21 21:04pm.
|
|
|
|
|
#ifdef NDEBUG
static
#endif
int _counter;
When the freakin' debugger doesn't allow you to see file scoped symbols.
|
|
|
|
|
This one I planed for tomorrow for Lounge *grrr* 
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Dirty is the normal way in C.
If there's any other way, please explain.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Here's some of my C goodness from the late 90s:
# ifdef __OVERRIDE__
# ifdef strlen
# undef strlen
# endif
# define strchr(str,ch) str_chr ( str , ch , CASE_SENSITIVE , NULL , NULL )
# define strcat(str1,str2) str_ncat ( str1 , str2 , 0 )
# define strcmp(str1,str2) str_ncmp ( str1 , str2 , 0 , CASE_SENSITIVE )
# define strlen(str) str_len ( str )
# define strncat(str1,str2,n) str_ncat ( str1 , str2 , n )
# define strncmp(str1,str2,n) str_ncmp ( str1 , str2 , n , CASE_SENSITIVE )
# define strrchr(str,ch) str_rchr ( str , ch , CASE_SENSITIVE , NULL , NULL )
# define strstr(str1,str2) str_str ( str1 , str2 , CASE_SENSITIVE , NULL , NULL )
# endif
|
|
|
|
|
 Oh yes something like this I also remember
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Today I had to call a function taking two int pointer arguments for returning some stuff. But I wasn't interested in those returned values (I tried with 2 nullptrs but fail) so:
int result = peskyFunction(new int,new int);
|
|
|
|
|
Won't those two int's leak?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Absolutely (100% incontinence) but:
1) it was some demo PoC
2) that function is initialization stuff so it will only leak once (or rather twice  )
|
|
|
|
|
I'm almost certain everyone here is dirty. This is all that it takes:
(void*)pValue
It's even more exciting (meaning dirty) coming out the other end...
|
|
|
|
|
I think most programmers aren't to keen on personal hygiene 
My blog[ ^]
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
