Don't forget that it was in the snow too with holes in your shoes

Don't forget that it was in the snow too with holes in your shoes :).

But hey, I'm one of those people that actually did have it pretty rough and I grew up somewhere that was the equivalent of the US in the wild-west.

Re: Why is it always uphill both ways to school?

I love it when all the code finally comes together in Perl myself. And the fact that it's practically self-documenting is a bonus. Here's a snippet:

@P=split//,".URRUU\c8R";@d=split//,"\nrekcah xinU / lreP rehtona tsuJ";sub p{
@p{"r$p","u$p"}=(P,P);pipe"r$p","u$p";++$p;($q*=2)+=$f=!fork;map{$P=$P[$f^ord
($p{$_})&6];$p{$_}=/ ^$P/ix?$P:close$_}keys%p}p;p;p;p;p;map{$p{$_}=~/^[P.]/&&
close$_}%p;wait until$?;map{/^r/&&<$_>}%p;$_=$d[$q];sleep rand(2)if/\S/;print

;)

Not so much up hill...

I find that this is always a misconception when the reality is, you are always walking into the head wind. You usually lean forward to push your self so you end up walking similar to up hill, but no matter. In reality you are always going against everyone else's standards, sometimes even your own.

I am going through 7 years of files realizing how much I lack a sense of organization.

Re: Why is it always uphill both ways to school?

I know, we all have different standards. I am sure that what I find sensible, someone else gets confused by. Part of the problem is that I cut my teeth on a mainframe, was taught by mainframe people, and grew up with a father who was a mainframe guy. So I am deeply steeped in the procedural code style, and the OOP stuff is a trainwreck from that perspective. ;)

J.Ja