Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Rooster]

I don't think using s.rjust is a good option because I really don't know it's function.
I'll do only things described in the book for now

[Rooster]

I have so much to do this week that I can't even touch the book for an hour

Hopefully I'll get some time on weekend

[Rooster]

Good god, was I procrastinating
It's like a plague.
At least I got better. I have to fight procrastination, and so I'm reviving this thread, and I return to python.
Wish me luck for I have ran out of it, when I was fighting my bad habits last time.
I'll pick off where I left, and look through everything I have done so far.

[eerr]

Whats up now.

[Rooster]

Not much.
Going through it slowly.
I hope my poor math skills won't interfere with learning

[eerr]

There really isn't serious math in making personal programs work, usually.

Now making stuff super efficient, is another matter.

I'm sure you'll do fine.

[qwertyuiopas]

Similarily, a regex is a very powerful tool, but you shouldn't need to use any for a very long time. If you already know them, they are easy and useful, but since one could easily look like this...

Spoiler (click to show/hide)

Code: [Select]

[:;]-?[\]\)\|<\(\{>\}]

If you know perl or use grep, you should have a decent grasp of them already, otherwise it is best to wait a while. A Long while.

[Rooster]

I have seen 1 kilo bytes rogue likes look like that.
I couldn't decipher anything.
Looks like programming is problem solving.
Since school isn't about that, looks like I'll be learning something usefull.
But those exercises get complex real fast.
That really bothers me.

[qwertyuiopas]

The diffrence, I guess, is that a regex, in python at least, is in quotes

Code: [Select]

R"<expression>"While very compact coding is even harder to understand. That particular example I gave looks for a wide variety of  text-faces, so naturally it must contain many odd characters. Further, many of those are preceeded by a \ because otherwise they would be considered contol characters.

[Googolplexed]

Is it just me, or is this topic a mess when it comes to teaching someone to program.
*Compiler optimistion.
*regex
Both very useful to know.. LATER

For now lets concentrate on the basics instead of arguing over sematics that Rooster can't comprehend yet.

As for the exercises, going through them one after the other is never really the best way to learn to program. You know simple I/O(Displaying text and inputing text) and basic control structures(IF, various loops) Then go and try to make something.
IMO I would suggest maybe making a simple text adventure

Learning to program by doing the simple exercices in a book will get you no-where. Learning string manipulation is useless unless you know when to apply it, 90% of programing books forget this.

The best way to learn programming is by trying to solve your own problems, take an easy task, like a text adventure and you will be surprised how many problems you encounter and how much you learn

[qwertyuiopas]

Try this, then:

Try to make a program that does simple rot13. At a bare minimum, it takes a series of capital letters from the user, and gives the rot13 result. Above that, try to allow spaces(wouldn't be affected) and preserve capitalization.

[Rooster]

Googolplexed: Well, thank you. I was actually trying to complete those exercises, but I've met only with failure. I think I'll do just what you recomened and just omit them.

I wonder If moding DF will give me any programing experience? 
Oh well, at least I should make a star craft mod like I promised.

[eerr]

Edit 2:
Going by what you have on the previous page, how is the roguelike going now?

Just curious iabout anything slowing you down.


Also, I totally finished a program for printing a right-aligned table of powers yesterday.(in C)
Managed to fix a problem where I constantly caused segmentation faults >.<.

Spoiler (click to show/hide)

Code: [Select]

int length[4];
int power;
while(1){
length[power];
power++;
if(power>=5)break;
}was causing the problem but was impossible to find, because the segementation fault appeared from printing my array of strings!

[qwertyuiopas]

In C, I find a reasonable way to get a string version of a number is

Spoiler: getting far off topic here (click to show/hide)

Code: [Select]

char numbuf[UNREASONABLY_LARGE_NUMBER_USUALLY_OVER_ONE_HUNDRED];
char *numstr(int num)
{
    sprintf(numbuf,"%d",num);
    return numbuf;
}
It assumes that the maximum it will ever have to write is under UNREASONABLY_LARGE_NUMBER_USUALLY_OVER_ONE_HUNDRED, but otherwise it means you don't have to worry about allocations, memory leaks, and it compresses it down to one function call.

Naturally, you would need to understand that getting a second number will overwrite every refrence to the first...

It would be easy to write a second version that then malloc()s and memcpy()s to return a reusable instance of the string-converted number, and while you are at it, why not add reference counting so that you can treat it like a string in higher level languages?

Of course, that does negate the whole benefit of simplicity that the original has...

Edit:

Spoiler (click to show/hide)

Code: [Select]

int length[4];
int power;
while(1){
length[power];
power++;
if(power>=5)break;
}

If that is a copy of the actual code, not initializing power can cause a hidden bug, that varies based on the whims of the stack...

[Googolplexed]

Googolplexed: Well, thank you. I was actually trying to complete those exercises, but I've met only with failure. I think I'll do just what you recomened and just omit them.

I wonder If moding DF will give me any programing experience? 
Oh well, at least I should make a star craft mod like I promised.

Don't treat it as an excuse to do nothing
As I said, make a text-adventure, or do what qwerty said, a rot-13 encoder. Either one is a good learning experience.

And I'm afraid that unless there is proper scripting (Not triggers AKA starcraft map editor) and not config editing(DF) that it won't help