PLEX86  x86- Virtual Machine (VM) Program
 Plex86  |  CVS  |  Mailing List  |  Download  |  Computer Folklore     

Peter_Jensen is a fake


VPN Service Provider

The Not_So_Great whitespace agrument
Hi PeterJensen, Re: How coding has been my sole source of income since the start of 1982, all without ever being sued or fired... and how...

Sorry about that Pete... won't happen again.

If you ever get contracted to code for someone ( unlikely, I know ),

Coding has been my sole source of income since the start of 1982, not once have I been sued or fired... What about you ?

I use VisualStudio to edit-manage articles that X.EXE downloaded-inserted into Cola.TXT as well as e-mails downloaded to In.TXT

I also use it to complie X.CPP, of course. I'd like to eventually remove that requirement, making X more portable. VisualStudio is a monster, many gigabytes, many places don't have it installed or won't grant me enough access.

Re: Why you so-called programmers only focus on trival issues,

Ridiculous warnings make ridiculous code. 14050
Just to keep in practice... :-) I've already seen Jeff Relf's response so I know he's seen this already. In comp.os.linux.advocacy, Kelsey Bjarnason wrote on Tue...

I can only buttume that you must have removed the common sense particle when you went inside your own brain I'm glad my sense isn't as common as yours.

Re: int rv, my SuperTemp, a global that I use a lot,

rv is not used in threads.

Bad code... hard to read, you say ? I'm not at all convinced.

Re: How I use int instead of bool,

It may be stored in the space of an int, but then again, it may not. You can't know that when you write the code,

Why is the size of a bool giving you trouble ? It's never been an issue with me.

Re: How I avoid dowhile loops for the same reason I avoid postincrements, because placing conditions-increments as up front as possible, means that I don't have to worry about them later,

When I start the do...while loop I also write the end immediately.

You, Pete, know little about coding. Same goes for Spooky. Because your statement above, as well as a similar one from Spooky, tells me that you guys have failed to realize that code gets Read as well as written... a big NoNo in my book.

This code is a thousand times more readable than your dowhile loop because the essential stuff is right there, up front and center: int Ch ; const int CtrlR = 0x12, Esc = 27 ; while ( doupdate(), ( Ch = getch() ) != Esc ) switch ( Ch ) { case KEYTSTP: handletstp(); handleresizesignal(); break;

Re: #define LoopTo( StopCond ) while ( Ch && ( Ch = ( uchar ) * ++ P , Ch2 = ( uchar ) P 1 , Ch ) && ! ( StopCond ) )

because your crap macros don't work with them. That should be a hint about that quality of your macros.

LoopTo() is as useful as hell, better than anthing in the STL, I think.

Re: typedef char * LnP ; typedef LnP * LnA ; struct LnT { LnA BB, PP, EE ; };

Now you're actually hiding the fact that you're working with a pointer ?!? I know it's a pointer, just like I know SvP and TbP are pointers, and LnA, SvA, TbA are arrays of pointers. and LnT, SvT, TbT are dynamic arrays.

If you can't or won't take the time to learn that about my code then you just didn't invenst enough time... that's your fault, not mine.

Re: How you created a funtion that's only called once instead of: int Sig = { SIGTSTP, SIGTERM, SIGINT }; Loop( sizeof Sig sizeof * Sig ) signal( Sig J , mysighandler );

No, you hid the code and made it less readable, in my opinion.

If we were working on a project together, one that actually delivered code to paying customers, I'd expect other issues to have a much higher precedence, ..or I'd expect to lose those customers.

Re: The investment required to learn my Loop() and LoopTo() macros,

as opposed to a function or language construct that does the same, then the macro is poorly written. Take a look at the ncurses implementation if you want to see how well-written macros work. Lots of the more trivial functions are actually macros, but you would never have known Why not just search for #define ?

Re: #define MINXSIZE 40 #define MINYSIZE 19 #define GREENONBLACK 1 #define REDONBLACK 2

Yyyyuck ! const int MinYSz = 19 ; would be far far better.

Re: #define KEYNEWDATA ( KEYMAX + 1 ) #define KEYTSTP ( KEYMAX + 2 )

Where is KEYMAX defined ? I can't find it.

Regex Pattern Matching algorithm in monoc
JeffRelf I'm looking at the source code for mono's Regex implementation right now. You can download...

Re: #define BRIGHTGREEN COLORPAIR( GREENONBLACK ) ABOLD #define BRIGHTRED COLORPAIR( REDONBLACK ) ABOLD

God I hate all-caps like that, how can you stand it ?

Re: How you and Spooky can't understand my macros,

It's always funny when somebody that's obviously completely incompetent

You and Spooky are just nitpicking for the hell of it, I imagine.

I don't know if my MSC complier would compile your code or not, and I'm not in the mood to find out, but that's how I'd judge one's competency... by what the code does.

Re: How it's always going to be hard to learn someone else's code,

it takes less time for a stranger ( who is send in the art ) Ok, now I Know you're a fake. By your definition above, the guy who wrote printf("Hello World.") is the best coder there is.

I always encourage rewrites, by the way, nothing better than a fresh start, I say.

Re: Using main() instead of int main(),

The implicit return value of a function is 'int', but that's a leftover from old C compilers.

Not returning anything when using main() instead of int main() prevents this Error in MSC: error C2561: 'main' : function must return a value. see declaration of 'main'

Leave the int off, and not so much as a warning will appear even when using the highest level of warnings.

it will show an error if the last app run returns a non-zero value. That's because the convention WinXP's Cmd.EXE is totally silent, it says nothing about the return value. When, exactly, would someone want to check nDUmeter's return value ?

gcc is crap, MSC is one bad-butt complier. Likewise, VisualStudio is one bad-butt debugger-editor. vi and emacs are crap, as far as I'm concerned.

Re: How I never get hung up on whitespace like you guys do, instead, I just change it to taste,

if you ever have to work with others. Not only is it annoying to read, I typically change whitespace when I read, even when reading my own code. ..it leaves a trail, indicating what I have, and have not, looked at.

You, Pete, are the only one worried about getting fired. What does that tell you ?

Re: How too many comments-files-funcions-lines get in my way,

They don't, really... I just modify them to taste.

in a way that often makes no difference to the resulting executable, You and Spooky never take the time to lean Loop(), LoopTo() or LoopXx(), instead you unpleasant woman about it being too obfuscated, ..What is the point in that ?


Linux | Previous | Next

The Not_So_Great whitespace agrument

Linux Advocacy Newsgroups

Courage is hard to fine, while scoping is comparatively trivial