PLEX86  x86- Virtual Machine (VM) Program
 CVS  |  Mailing List  |  Download  |  Newsgroups

Thou shalt have no other gods before the ANSI C standard 1529


Your Ad Here

Your Ad Here

Thou shalt have no other gods before the ANSI C standard 1530
different I've never been sure how to respond to "so?" in any context. It usually indicates that the other person has no idea whatsoever what my...

I'm cutting stuff because it's getting cumbersome.

And I'm not of necessity talking about documentation. It may be "Hey, Rob, how in hell did you come up with this?" But yes, things do get lost to history.

Separate documentation, highly unlikely. But, as I noted earlier, some of us did (and do) in the code, but it's not common.

Well, in environments I've worked in managment made lab note books available and we often (but not always) did keep notes, though usually only after reaching the debug stage.

I apply the method back further than many of my fellows and, perhaps, you're doing.

Someone who replied to my message made an excellent example about getting cars fixed. At some point, you trust (or don't) a mechanic. But that's not really learning about fixing cars. But that's not (nor did the responser claim, I'm extending here) the same as trusting a teacher. From the mechanic, I just need to get the car running again. From the teacher (professor?) I need to learn how to fix it, program it, design it myself.

Well, of course it is. I tend to hook people by their signatures rather than see you as "-BAH".

Thou shalt have no other gods before the ANSI C standard 1531
YES!!! My apologies. I'm still trying to learn how write as well as you guys do. Sure...

My apologies to Mr. Reistad.

Probably.

- Bill



Your Ad Here

List | Previous | Next

Thou shalt have no other gods before the ANSI C standard 1530

Alt Folklore Computers from Newsgroups

The #1 Usenet Provider on the Internet

Thou shalt have no other gods before the ANSI C standard 1528