1. Oppinion...
- Posted by PQ <quistnet at HOTMAIL.COM>
Jan 25, 2000
-
Last edited Jan 26, 2000
------=_NextPart_000_003B_01BF677D.DD52FE80
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hy,
I want to comment on all you programmers who thinks that he/she doesn't =
make any mistakes. Here are some some tips you should NOT do...
- Separate programs, part of 1 program.
- Calling a pointer to the memory an integer, which should be an =
atom.
- Sizable windows while there's nothing more to see when resized.
- Using constant-statements constantly, while a comma will suffice.
- Using only constant-statements for the famous create() function, =
integer is also an option.
- Using e.g. wait_key() in graphics.e, while that's the same as
machine_func(26,0).
- Using only someone else 's include files, while you can make one =
adjustible for=20
your needs.
- Adding useless spaces between nothing¬hing or something¬hing.
- Placing comment without --.
I'm not perfect eather, but try to keep these things in mind.
Does someone like to add somethings to this list or remove something.
Bye,
PQ
QC
------=_NextPart_000_003B_01BF677D.DD52FE80
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hy,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2><BR>I want to comment on all you =
programmers who=20
thinks that he/she doesn't make any mistakes. Here are some some tips =
you should=20
NOT do...</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>- Separate programs, =
part of 1=20
program.<BR>- Calling a pointer to the memory an =
integer,=20
which should be an atom.<BR>- Sizable windows while =
there's=20
nothing more to see when resized.<BR>- Using=20
constant-statements constantly, while a comma will=20
suffice.<BR>- Using only constant-statements for the =
famous=20
create() function, integer is </FONT><FONT face=3DArial =
size=3D2> =20
also an option.<BR>- =
Using e.g.=20
wait_key() in graphics.e, while that's the same as</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> =20
machine_func(26,0).<BR>- Using only someone else 's =
include=20
files, while you can make one adjustible for </FONT></DIV>
<DIV><FONT face=3DArial size=3D2> your=20
needs.<BR>- Adding useless spaces between =
nothing&nothing=20
or something&nothing.<BR>- Placing comment without =
--.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>I'm not perfect eather, but try to keep =
these=20
things in mind.<BR>Does someone like to add somethings to this list or =
remove=20
something.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial =
------=_NextPart_000_003B_01BF677D.DD52FE80--
2. Re: Oppinion...
Just a few comments...
On Tue, 25 Jan 2000 21:48:07 +0100, PQ wrote:
>- Using only constant-statements for the famous create() function,
integer is also an option.
While this is true, I think it's better to use constants for Windows and
their components since these are things you typically do not want to
change. It prevents you from accidentally modifying a 'variable' that would
break your program.
>- Adding useless spaces between nothing¬hing or something¬hing.
While the spaces are useless to the compiler, they can add quite a bit to
the readability of your code (and they do not increase the size of your
program significantly).
-- Brian
3. Re: Oppinion...
- Posted by Lewis Townsend <keroltarr at HOTMAIL.COM>
Jan 25, 2000
-
Last edited Jan 26, 2000
Hello PQ,
You said,
>I want to comment on all you programmers who thinks that he/she >doesn't
>make any mistakes. Here are some some tips you should NOT >do...
>
>I'm not perfect eather, but try to keep these things in mind.
>Does someone like to add somethings to this list or remove something.
>
I'm not sure I can add anything but I would like to remove a few
and here are my reasons.
>- Separate programs, part of 1 program.
I'm not exactly sure I know what you mean but sometimes it
is very intuitive to break a "software package" into multiple
programs. Especially memory hogging programs. How would you like
to wait while the entire MS Office is loading if all you want to
use MS Word. I understand that this may not be what your talking
about, so if it isn't please ignore this.
>- Using constant-statements constantly, while a comma will suffice.
While I personally prefer to use the least abount of declaration
words as possible, repeating them in this way can enhance
readability, however slightly.
>- Using e.g. wait_key() in graphics.e, while that's the same as
> machine_func(26,0).
wait_key takes less keystrokes and is more readable. I really
don't understand why you disaprove of it.
>- Using only someone else 's include files, while you can make one
>adjustible for your needs.
While I understand and agree with the spirit of this comment,
I urge you to remember a few points.
1. authors create include files to be used by others.
2. often these files fit one's needs sufficiently
3. many include files provide easy access to functionality
that many prammers cannot create themselves.
>- Adding useless spaces between nothing¬hing or something¬hing.
They don't hurt anything. If you are talking about this:
x = a + 1
vs
x=a+1
then I would prefer the one with extra spaces as it is easier
to read. If you are referring to indentation like this:
procedure abc ()
if x then
xyz ()
end if
end procedure
then I must disagree again as this indentation also helps
readability. But if you are refering to spaces at the end
of a line that aren't followed by any comments or anything,
then I see your point. But as I said, they really don't
hurt anything.
These statements are my oppinion so please don't take offense
from my criticalness. We just disagree.
later,
Lewis Townsend
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
4. Re: Oppinion...
Hi PQ,
You said,
>I want to comment on all you programmers who thinks that he/she >doesn't
>make any mistakes. Here are some some tips you should NOT >do...
>
>I'm not perfect eather, but try to keep these things in mind.
>Does someone like to add somethings to this list or remove something.
>
>>- Using constant-statements constantly, while a comma will suffice.
I'm not sure that I completely agree with this. While doing the Morfit
include conversion to Euphoria from the Visual Basic include, the comma was
just fine. The Visual Basic include has almost nothing nested in with the
function statements. The C++ include that I have used now however, is chock
full of stuff (constant declarations, comments etc), spread out at random
through the include. My comma's could easily have been tripped up by their
constant declarations and I could see that getting it right was going to be
a headache.
I guess all I am saying is that all of us do stuff from time to time that
might look dumb to someone else. If it works for them, does it matter?
Mark
