i like the path in which the availability gets checked twice

this half step reminds me of the Velocity-Verlet-Algorithm http://en.wikipedia.org/wiki/Verlet_integration#Velocity_Verlet[^]

i would never use Ubuntu on my supercomputer :omg: they have an extra designed OS also for the clusters, Ubuntu is no good choice. It has to much standard features which maybe opt-out, but i prefer everything on opt-in!

Sometimes the code does not get correctly "reflected" by the Reflector, perhaps it is just a Compiler Optimization or so.

nevertheless the pointer is immediately dereferenced, so in this example it is perfectly OK :laugh:

one of the many "DON'TS" in C++ i hope this tutorial is just a "do not"

the link says, that using a bigger alphabet is more secure, but this is just plain wrong it is better to increase the number of characters, even, if they are simple (lowercase letters) simple math: say 'k' is the size of your alphabet and 'n' shall be the size of your password. then there are k^n possibilities. increasing n is much more valueble than increasing k. just try it out: f = @(n,k) k^n; f(6,40) = 4.0960e+09 f(6,41) = 4.7501e+09 f(7,40) = 1.6384e+11 f(10,60) = 6.0466e+17 f(10,61) = 7.1334e+17 f(11,60) = 3.6280e+19 f(20,60) = 3.6562e+35 f(20,61) = 5.0886e+35 f(21,60) = 2.1937e+37 as you see, increasing the first parameter (length) makes like 100 times more possibilites, while adding one more symbol is like not even doubling. so, a good password is a passphrase, take 3-5 random (and easy to remember) words and stick them together. the idea to use passphrases came from http://xkcd.com/936/[^]

the unequality test is more portable i actually used it in CUDA, afterwards i found out there exists an isnan(x) builtin function now porting to other languages is more easy

I dont believe your designer wanted it that way, but a comparison to a NAN is always false. I am using a similar NAN-Check if (x != x) ... gets true if x is NAN

Luc Pattyn wrote:

if ( ( (a==null) == false ) == true ) {...}

can you extend this recursively? only to be very very sure:

if ( ( ( ( ( (a==null) == false) == true) == true) == true) == true)

to shock afterworkers and make compiler happy, one could sometimes say == true and == false :laugh:

the method should be called RecursiveParentsForLoginId

GenJerDan wrote:

Ja, und hinterher ein Nasenbär und keiner weiss warum.

oh, der kam unerwartet. aber werde ich mir merken :-D

well seriously, you should read this book http://blog.oncode.info/wp-content/uploads/2008/02/rtfm.png[^] perhaps you didn't read well, because after 17 iterations you should have your relevant information, if not, read it 17 times again

sorry, but if you look at the MSDN C# Reference http://msdn.microsoft.com/en-us/library/618ayhy6.aspx[^] and hit C# Operators you can see them at glance. Looks like there is some RTFM to do :-D

Ian Shlasko wrote:

So what do you think? Too concise? Too LINQy? Or just right

absolutely right! i also prefer C# coding like this...it makes more like a functional language while keeping the good ol' imperative stuff. my colleagues are slowly going to use these neat feautures :>

i mean it! The glorious "How-Not-To Programming", or "The 99 Don'ts of Web Development"

with many many partial specializations, that would be something for the Coding Horrors :laugh:

Alex Fr wrote:

Looking at Template Template Template parameters, I think, maybe the filter was right...

:thumbsup: thats a good one! but dont get it wrong on Alexandrescu <- he is great Template Template Parameter are "ok" what i did here with Template Template Template Parameter (say that 10 times fast) was just a little joke^^

Template Template Parameter Following Policy Based Design from Andrei Alexandrescu, there is a certain need for template template parameters and after using them a while, you get quite used to it:

template <
class T,
template <class> class Policy

class Host {
};

But what when you pass a policy host as a policy to a greater host? I didn't even know if it works, so just tried out;

template <
class T,
template <
template <class>

class Policy

class Host {
};

For the sake of brevity, i made only one of those. in the real code there are 4 policies and 1 policy-policy with 4 policies I have to change this sooner or later...wrapping the Policy to a inner type or something.

Ray Cassick wrote:

You can use the best tools on the best platform using the best agreed upon methodologies and still write code that is ugly.

:thumbsup: