Planning to write a C++ Pre-Processor tut

Hey guys i am planning on writing a C++ Pre-Processor tutorial. Anyways, we will learn how to write macros and how to make header files and how to use them in your programs. Also, this tutorial will cover all of the escape characters (because i think they are important and think they are fun to use :)) and how to make comments in C++ (there is a cool way to comment things out in C++ using the pre-processor which ill teach you guys how to use). Anyways, if there is something you guys would like me to cover in the tutorial, let me know and i will try to add it in :)

Wow that sounds awsome....I think thats a great idea! Maybe you could list a few reference links to freeware compliers and tut sites. Good luck!

alright...will do also if you want ill add a list of books that really helped me out when i was first learning C++ :)

Sounds good looking forward to it

/*sounds like a plan*/


I will enjoy reading it.

One idea: You could provide some basic Unix commands as well for all the windows people.

But the preprocessor sucks, macros suck, and there are better ways of doing them in C++. Most compilers do inline functions, you know, which are vastly better than macros.

Anyway you want to know why C sucks?

http://www.projectz.org/index.html%3Fid=182.html

sound like fun...but I am sort of mastacistic (or somthing like that ) bring on the tut. :D

Slarty no offense but half of the argument in that link you gave is that people new to the language won't know the syntax.

Just because it's not in straightforward english so that anyone can read it doesn't mean it's a bad thing, using shorthand can speed up the time it takes to code things because you don't have to spell out long words all the time, and on top of that most of the shorthand used makes reasonable sense on its own.

The point on the pre-processor is true however, but I've never had to define variables with it, I really don't see the point. If you need to define a variable then use the if built into the pre-processor, define should only be used for setting things that control code alteration like what OS the code is compiled on, etc...

The assignment syntax is fine, sure the == part can cause grief at first but the concept isn't that hard to wrap your head around, most people I know never considered it a problem when they were learning. As for x = y = 456, the assignment operator works from the far right first and assigns to the left, that simple, there's no tricks to it.

The ternary "?" operator is very useful for adding conditionals in places where you just need a quick if/else and are only returning variables based on it. One of the handiest places to use this is when formatting text for output, you can put it right in the output statement.

For loops are no good? Maybe the author should look at their code, because he messed up the while loop that "emulates" a for loop, the i++; should be at the end of the loop so that it increments in the right place. A for loop keeps the incrementing and initialization in a common place making it easier for a newbie to see what the loop is doing, the 0 to whatever is just something that you get used to, many compilers count 0 as the first number, learn it and get over it.

The fact that anything can be used as boolean is extremely handy, sure without proper naming it gets confusing but otherwise it makes checking things nice and simple.

I will agree with the strings though, c was awful for strings, c++ is a big improvement in that area, while there are still places where it could be better.

Pointer arithmetic is fairly straightforward, if you pass the memory location of a character to the character formatter in printf it prints that character, to the string formatter, it prints from that memory location until it finds the null. the memory for a single variable is sequential, it doesn't got 0,3,2,6,1,4,5 it goes 0,1,2,3,4,5,6 so referencing the 3rd character in the variable is a simple task of adding the appropriate number to the pointer, ie memory address, or using the variable as an array which does that for you.

Multidimensional arrays... I seem to recal using them in c, and c++.. sure they're limited by size constraints which is a pain but that's where vectors come in in c++... Yes I'll admit I like c++ much more than c simply if simply for the stl and streams.

Typdefinition makes for easier readability in most cases, I really don't see what the authors problem with it is...

Default scope is global? I seem to recall that if you define a variable in a function it lived and died in that function but never left it. If the author ment that it was global if defined outside any functions in the code then yes.. that would usually be where you declare global variables. And while static isn't the best keyword they could have used it's not all that out of the blue.

Modules take some getting used to but would you rather read a file that's 3,000,000 lines long or have many little files that you can read over and see what it's doing without getting lost in the code? This makes it easier to read and modify.

I do agree with the printf being error prone.

While there is truth to some of what you say, a lot of it isn't all that accurate, you leave out why the "feature" was put there in the first place. C is not by far the best language out there but it's small and easy to write little programs with little code, something Java makes a chore out of, and it's fast.

As for the pre-processor tutorial, to get back on track, I think it'd be a great idea. But when you write it keep in mind the problem that Slarty pointed out, #DEFINE shouldn't be used to declare variables in most cases and if it is you should put brackets, "()", around the definition to keep the order of operations intact. If you purposely need to have the side effect that Slarty mentioned happened then chances are you don't need that tutorial.

Hey Eskimo, this sounds like it's going to be the Tutorial of all Turorials.

I'm looking forward to it, i have just finished learning html
and im looking for something else to learn.

Although i might need to start with the basics, and work my way up to C++
As i heard you need to learn C first, so would that be correct?

Anyhow Hello to you all.

And what a wonderful place this is......

Quote:

---

As i heard you need to learn C first, so would that be correct

---

Well creative, there are mixed views about that. I personally never learned C before i learned C++ and i was told that if i did i would develope bad habits...anyways, you could learn it, but you dont HAVE to know any C in order to understand C++.

Quote:

---

DEFINE shouldn't be used to declare variables in most cases and if it is you should put brackets, "()", around the definition to keep the order of operations intact.

---

Very true...i will have some examples of what NOT to do and how working with the preprocessor can result in some bad errors. Also, i will explain some usefull things that the preprocessor can help you with.

Quote:

---

But the preprocessor sucks, macros suck, and there are better ways of doing them in C++. Most compilers do inline functions, you know, which are vastly better than macros.

---

True indeed slarty--but you have to understand all because something sucks doesnt mean that we shouldnt learn it...There are different ways of doing things in C++ that dont involve the pre-processor and i will mention some of them to you guys in my tutorial. About inline functions, well, sure they could work, but it never hurts to know a little bit about the preprocessor :)

Anyways, i currently have written only 2 pages (my tutorials normally tend to be 5-6 pages long), so dont expect this to come out any time soon. I have a history test and a french test this week, so plan on it coming out next week some time...after the weekend so i can wrap stuff up. Anyways, i am looking forward to it :)

well slarty quite good arguments...i wud say...but countered well by Pecosian...cheers Pecosian....

i wud just like to add a few lines ....

it seems the article, which seems to be written by u, is from a frustrated C newbie....who havent tried to code a lot...just started and got wired and left....and blamed it on C....
the very first thing...C was never meant for everyone....it was by the leets for the leets....
C gives u enourmous power. u think of anything which cannot be solved using.....one or the other way C will let u do anything.

Yes, it very easy to screw ur code while coding in C...anyhow it wasnt ever supposed to be VB..

U can learn enourmous things from C....just try to be leet in C.

#include<noob_programmer>

#DEFINE you slarty


int main()
{
if( you == confused.)
printf("syntax for every language can be confusing at first");

if(your_program == in_c)
printf("LEVEL 2 Programming language makes for a faster executable");
else
printf("I really hope its not java");

return 31337;
}

ehm, after the #define command everything should be written with uppercase letters and WITHOUT SPACES
so, dont laugh at slarty when you can't even code.

it's slarty's opinion and he supported it with arguments. nothing's wrong with that.

lol... I didnt realize I was writing actual code, if you wanted me to I could make the actual program for you

lets see so why didnt you tell me that i didnt include everything I needed and that certain variables are undeclared.

Slarty is entitled to his own opinion and so am I. My point is every language has a syntax you must learn(hence the term 'language') and that C is a lower level language and will run faster on most Intel processors.

As for not being able to code..hmm I tied 4th place in the TopCoder 2002 coding challenge at SunOne and I am the lead c/c++ programmer for an IDS company so I must be doing something right.

at least you could get the #define thingie right =pp

ok

#define YOU (slarty)