Section 19.3
The line terminator for message-header fields is the sequence CRLF. However, we recommend that applications, when parsing such headers, recognize a single LF as a line terminator and ignore the leading CR.
426 karma · joined June 9, 2008
Section 19.3
The line terminator for message-header fields is the sequence CRLF. However, we recommend that applications, when parsing such headers, recognize a single LF as a line terminator and ignore the leading CR.
"Your bytes or your life!" just doesn't have the same ring to it.
The American Dream is truly a wonderful concept.
>Her studies found that in perfect use -- meaning the man pulls out every time -- withdrawal has a 4 percent failure rate, as compared to condoms, which have a 2 percent failure rate.
>"But nobody's perfect," said Jones, who published her commentary in the June issue of Contraception magazine.
So, if nobody's perfect, I would say we need more research before drawing conclusions one way or the other.
I had a good chuckle at the index flowchart - maybe I'll give TAOCP another shot - thanks.
Knuth has a sense of humor - who knew?!
Opera has an excellent way to select links using spatial navigation (shift+down,+up,+left,+right). It's remarkably easy to navigate to any link quickly on the page.
Also http://www.opera.com/browser/tutorials/nomouse/ is a good place to start "keyboard-only" browsing.
It's not that I have anything against the mouse but I enjoy the workflow and it works very well for me. Plus I don't have to worry about adverts or drive-by infections most of the time :-)
>Select the text you want to convert, hit :, then enter the regex:
s/\<\(\w\)\(\w*\)\>/\u\1\L\2/g.
And, even this is not completely correct. The expression will not work if you select part of a line. Your best bet would be to remap the following: nnoremap <A-c> :s/\<\(\w\)\(\w*\)\>/\u\1\L\2/g<CR>
vnoremap <A-c> :s/\%V\(\w\)\(\w*\)\%V/\u\1\L\2/g<CR>
To get key bindings that you like (I've defaulted to the EMacs capitalize-word binding).I'd hire him in a heartbeat.
However, if I had RSI problems I would switch to something else - it's definitely worth learning a new tool if it helps my health and well being.
Give me a shout when you're down the next time and I'll put together a team to thrash you at kabaddi! :-)
All I'm saying is that if you have to go through so much pain and trouble to use a piece of software then just maybe it's not right for you.
Also I'm not suggesting Vi but Emacs has a pretty good Viper-mode that may help with RSI issues. I use EMacs with Viper and I can pretty much work with minor hiccups when I switch from Vim. Just a suggestion.
EDIT: Whoops! Sorry - my bad! Thanks paraschopra.
Also I'd guess Zaid is an expatriate - simply because I've noticed this tendency to put down India mostly among ex-pats (in the US and UK).
I'm a native and I love India. I've had chai at a dozen houses and shops and I never dreamt of feeling suspicious (and nothing happened to me either).
EDIT: To clarify my last statement - many shopkeepers will offer you tea when you are buying something from them.
Of course you can also meet some really horrible people but I think it's the same anywhere in the world. You have to keep your guard up a bit when dealing with total strangers.
>1995 - Brendan Eich reads up on every mistake ever made in designing a programming language, invents a few more, and creates LiveScript. Later, in an effort to cash in on the popularity of Java the language is renamed JavaScript. Later stil, in an effort to cash in on the popularity of skin diseases the language is renamed ECMAScript.
In fact, C++ still carries the "inline" declaration around to avoid function call overhead. The compiler can ignore when knows better but the fact that inlining exits implies that function call overhead is not imaginary.
Firstly it is a focus on "results" rather than output. The novice has produced a lot of output but no results. How would you evaluate if the components serve their purpose? Are they doing too much? Are they not doing enough? It is only by virtue of the program's results that you can check. As programmers we tend to evaluate the code (which is an internal focus) more than the running program (which is an external focus). This is a great way to learn but a bad way to deliver anything of value to an end customer.
As a programmer, the novice would understand and be interested in the ins-and-outs of his screen editor, gui routines, and AI module. However, he would probably not have the same level of understanding of finance. For a good product, the novice should concentrate on raising his understanding of finance to the level where he can deliver solutions to his users. By ignoring his users (delegating them to an afterthought), he is making a fundamental mistake.
Finally, it is a question of value. This is key - the most fundamental aspect of this scenario. The programmer, for all his effort, has delivered nothing of value to his users. Worse, he does not even have the attitude and direction required to deliver value. When someone says "I'll put in that stuff later" (or it's equivalent), you can be sure they will deliver something of poor quality to the users.
In the end, if you cannot say the work you have done today will make someone's life better - what is the point of working so hard?
>The novice worked furiously for many days, but when his master reviewed his program, he discovered that it contained a screen editor, a set of generalized graphics routines, an artificial intelligence interface, but not the slightest mention of anything financial.
>When the master asked about this, the novice became indignant. ``Don't be so impatient,'' he said, ``I'll put in the financial stuff eventually.''
I love this one because it took me many many years to "get" this lesson: it's not about the code. It's about the Program.
EDIT: Minor edits
And her IQ is 131 (higher than mine).
EDIT: Grammar