[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    kdenonbeta/kio-rio
From:       CVS by charles <kde-cvs () kde ! org>
Date:       2000-10-11 9:23:22
[Download RAW message or body]


kdenonbeta/kio-rio Makefile.am,NONE,1.1 README,NONE,1.1 binary.h,NONE,1.1 \
crio.cpp,NONE,1.1 crio.h,NONE,1.1 program.cpp,NONE,1.1 program.h,NONE,1.1 \
                rio.cpp,NONE,1.1 rio.h,NONE,1.1 rio.protocol,NONE,1.1 \
                rioserv.cpp,NONE,1.1
Author: charles
Wed Oct 11 09:23:22 UTC 2000

Added Files:
	Makefile.am README binary.h crio.cpp crio.h program.cpp 
	program.h rio.cpp rio.h rio.protocol rioserv.cpp 
Log Message:
kio-rio stuff!!!

Read all my profanity in the README file, (or else)
I mean it, you're doomed if you don't read the README!
Read the entire thing, because it's late, I'm tired, and I'm a bit
rambly, as you may be able to tell by the content of this log.

Remember that this only works on the parallel Rio, it really doesn't
work at all.  It will not, I repeat, It Will Not do anything but
list files off your rio.  I mean it, it sucks THAT much, if not even more.

It's really quite horrid.

Oh, and if you want to modify it. Go ahead, perhaps if you make it better.

Also, if you want to edit it, _indent_with_friggin_tabs_.

People always give stupid reasons for not indenting with tabs.
While I know the reason: arrogance.  Sheer friggin' arrogance.
Someone started it off to be different, and someone joined, and all of
a sudden, everyone has forgotten how much happier than tabs, just
because they've replaced thier /boot/vmlinuz with a symbolic link to
/usr/bin/emacs and think their so hot now.

Why don't you people come up with a SINGLE good reason to indent with spaces
instead of tabs that I can't come up with an answer to. Come on, I dare
the lot of you.

The first one I can think of is that tabbing makes everyone happy because
the person with the text editor can decide how many spaces every tab is.
Then while I prefer my tabs 4 characters deep, there's certain freaks that
prefer 8 or 2.  Well, they can friggin customize it without anyone knowing
by setting a stupid number in their text editor.

Now you'll say: what if I need to format my code?

Ok then, here's a concept:

TAB if ((somelongbooleanstatement) &&
TAB     (someotherlongboolean statement))
I'm impressed, now no matter what tab width I use, those parentheses line
up JUST the way I want them to!


[prev in list] [next in list] [prev in thread] [next in thread]