~$ cd Code
~/Code$ find . -regex ".*\.\(php\|c\|h\|cpp\|hpp\|cs\)\$" -print0 > list
~/Code$ wc -l --files0-from=list
362698 total
Not including code for work, of course.
Feschotte said this virally transmitted DNA may be a cause of mutation and psychiatric disorders such as schizophrenia and mood disorders. In his article, Feschotte speculates about the role of such viral insertions in causing mutations with evolutionary and medical consequences.
The article doesn't go into much detail, but one type of virus that looked at specifically is a brain virus, definitely interesting implications for mental health research.
It is preferred that the client not support outside protocols such as AIM, MSN, Yahoo, etc.; if it does, I will have to promulgate and enforce yet one more policy that my techs not connect to them.
It sounds like your network, which contains confidential medical records, is connected to the internet.
So I have just one question: Dear God, why?
This just emphasizes what we already knew about C, even the most careful, security conscious developer messes up memory management.
This doesn't follow from TFA. The blog points out two instances of buffer overflows. The first one you could argue they messed up "memory management" because they used the wrong bounds for their array in several places... but they don't sound very "careful" or "security conscious" since checking to make sure you understand the bounds of the array you're using is pretty basic.
But that's not what bothered me. The second example is a typo where TFA says someone entered a "3" instead of a "2". In what dimension is mis-typing something "messing up memory management"? That just doesn't follow.
"No matter where you go, there you are..." -- Buckaroo Banzai