Skip to main content

Posts

Showing posts from April, 2006

Recognizing Strokes

STROKE: Remember The 1st Three Letters...

February 01, 2006

My friend sent this to me and encouraged me to post it and spread the word.
I agree. If everyone can remember something this simple, we could save some
folks. Seriously.. Please read:

STROKE IDENTIFICATION:

During a BBQ, a friend stumbled and took a little fall - she assured
everyone that she was fine (they offered to call paramedics) and just
tripped over a brick because of her new shoes. They got her cleaned up and
got her a new plate of food - while she appeared a bit shaken up, Ingrid
went about enjoying herself the rest of the evening. Ingrid's husband
called later telling everyone that his wife had been taken to the hospital
- (at 6:00pm, Ingrid passed away.) She had suffered a stroke at the BBQ.
Had they known how to identify the signs of a stroke, perhaps Ingrid would
be with us today. Some don't die. They end up in a helpless, hopeless
condition instead.

It only takes a minute to read this...

A neurologist says that if he can…

Perl Inline

Perl never runs out of wonderful stuff to offer. Ever thought of inserting C/C++ code inline in Perl? That means running compiled code and interpreted code side by side.!

http://www.perl.com/pub/a/2001/02/inline.html

Debian-package exists as below:
mynixbox:~# apt-cache search perl | grep inline
libinline-octave-perl - Perl5 module to Inline GNU Octave code
libinline-perl - Write Perl subroutines in other programming languages
libtest-inline-perl - Embed tests and code examples in PODAlthough I haven't tried it yet, I think this would be ideal for cronjobs, which need to do the same thing again and again.

Major efficiency can also be gained by being able to include pre-compiled libraries which need not be compiled at Perl-run-time.

Code Versioning - CVS or SVN?

Tough question as I have experience with neither. While I tend to go with older, more established systems as it's easier to climb the learning curve with abundant reading material and support, it sounds like going for SVN might be anologous to having chosen Postfix over Sendmail to run all my mail.

Postfix decision was made some 5 years ago and it was meant to be a rework of Sendmail at the architectural level and security taken into consideration, but essentially the same features as Sendmail. Looking back, with no security issues and managable administration (even I could handle it :) I think that was a good call.

For the same reason SVN looks like a good choice, even though the system has been around for only a couple of years (2004?). It might help us to scale into future better and coming from (most ly) the original developers of CVS, it should be a continuation, and not a radical diversion, of the mature but aged CVS.

I haven't read about any major limitations of SVN, …