🔒 Locked

Writing Clean Code....?

Started by cippyboy Mar 21, 2003 at 1:44 PM 9 replies 450+ views

Original Post

Mar 21, 2003 at 1:44 PM

Can anyone lend me some theory about how some clean code would look like ? I`m trying to imagine the code with lots of classes and also well arranged in a page... like buga buga() { buga1(); buga2(); ....... bugaX(); } Can anyone give me some more examples/tips ? PS:Just curios about how other people write code....

Arild Fines

138

Arild Fines

Mar 21, 2003 at 2:08 PM

Clean code doesn''t have names like "buga"

"If there is a God, he is a malign thug."
-- Mark Twain

origil

Mar 21, 2003 at 2:23 PM

quote:
Original post by Arild Fines
Clean code doesn''t have names like "buga"

"If there is a God, he is a malign thug."
-- Mark Twain

Well, if you ask me, "buga" is the way to go!
I''d be able to answer if you were a bit more specific.

v_d_d

Mar 21, 2003 at 2:47 PM

I would rename your functions to MyBuggyFunc1(), MyBuggyFunc2()... etc...

At least, if not clean, it will be honest...

;-)

redragon

Mar 21, 2003 at 2:51 PM

quote:
Original post by cippyboy
Can anyone lend me some theory about how some clean code would look like ?
I`m trying to imagine the code with lots of classes and also well arranged in a page...
like
buga buga()
{
buga1();
buga2();
.......
bugaX();
}
Can anyone give me some more examples/tips ?

PS:Just curios about how other people write code....

Don''t know exactly what you mean, but:
http://www.doc.ic.ac.uk/lab/cplus/c++.rules/

Here is a good start. Really, you don''t want to just break out segments of code like:

  
doSetup();
doProcessing();
doDrawing();
doPostDraw();
doSomeStuff();

What you want to do is try to break things down so you can explain it easily (IMHO).

  
// Transform the current entity object by it''s possition and rotation.

CMatrix matTransform;
CMatrix matRotation;
matTransform.setToTranslation(entCurrent.getPosition());
matRotation.setToRotation(entCurrent.getRotation());

entCurrent.transformBy(matTransform * matRotation);

Now obviously there are holes in what I''m saying here, but try to simplify without obscuring what you''re doing. You want it to make logical sense. You''ll notice that I don''t follow the rules in the document I attached, but I just recommend it as a guideline. Don''t know if I''ve helped or not. Good luck.

- sighuh?

TheAIDSVirus

Mar 21, 2003 at 2:55 PM

This is a question that has a thousand not right, but not wrong, answers.

Clean code is consistent code. That''s about the only solid rule. Decide on a style and stick with it.

----
AIDS

llvllatrix

Mar 21, 2003 at 5:02 PM

I also find that clean code means encapsulation. As you program grows, encapsulation will really help you keep it from becomming spaghetti (or in my case, soup

).

With demos its usually easier to separate classes into modules - one class per module. That way if you need it for another project, you just include the module and you''re done - that is a sign of clean coding.

DalTXColtsFan

Mar 21, 2003 at 9:43 PM

Well, I don''t know about how to WRITE code, but if I gave you some links to some of *my* projects I could sure as shootin show ya how NOT to write code :D

RipTorn

Mar 21, 2003 at 10:24 PM

if another programmer can look at a RANDOM block of your code and know what it is doing the first time they read it, it''s good code.

| - Project-X - my mega project.. getting warmer

- | - adDeath - an ad blocker I made - | - email me - |