|
Back in the early years of my programming career I started with asm programming. I still remember how happy I was when I first put together a "for loop" in an assembly program (at home, I wasn't forced by teachers). It was something that read in some input from the keyboard and then printed it the the screen when the enter key was pressed or something similarly stupid stuff. In assembly even this simple program was a challenge for me despite the fact that it was only a stupid for loop (I didn't even knew that it was a for loop, I only knew that I require a few jumps and condition checking). You have to search for a challange that keeps you motivated but isn't too far beyond what you can achieve with your current knowledge. If that knowledge is zero then the first step is reading books and the code of others'. Don't try to skip reading 1-2 books on C programming, you will regret it and you will waste a lot of time by progressing with much slower speed by doing nothing because of being able to do nothing without the necessary basic knowledge. I can easily imagine that you think your biggest problem is the C programming language itself but you should quickly realize that the language itself is only a tool and the real value is the experience you gain by solving problems. Every language of the same paradigm contains the same basic constructs (loops, functions, classes, ...). The sooner you get through the learning of your first language (for example C) the sooner you can start with solving real-world problems and gaining experience in software design that is much more important than being able to produce compilable lines of code in a language. Without experience even the smallest problems seem to be unsolvable, it requires 1-2 years spent with valuable programming to learn the basic patterns (for example how to read in data and parse it, how to manage memory, ...) in order to be able to handle these naturally without effort by concentrating your efforts on solving the real problems built on top of the simple patterns.
|
|
|
|
|
Uh oh, its the pastapizza daily novel!
Hey, did you ever hear what paragraphs are? Try using them occasionally.
--edit--
I see a sense of humour is lacking in some.
modified 21-Aug-13 10:57am.
|
|
|
|
|
(but scaring at first sight  )
Veni, vidi, vici.
|
|
|
|
|
I'm good at writing scaring paragraphs. I have always been terrible in literature, grammar and similar things...
|
|
|
|
|
No no no no no!
It doesnt go 'Good Evening' it goes 'Hello World!'
Dear oh dear, how are you ever going to learn if you dont get this right!
|
|
|
|
|
Veni, vidi, vici.
|
|
|
|
|
Member 9857487 wrote:
how can i improve my c programming in different ways
Learn how compilers and linkers work. That knowledge will increase your understanding of how the C language works.
|
|
|
|
|
Hello. I'm trying to open exe file , but there is a problem like this:
<<assert failure="" in="" qlist::operator[="" ]:="" "index="" out="" of="" range",="" file="" c:\qt\4.8.1\include\qtcore\..="" ..="" src="" corelib="" tools="" qlist.h,="" line="" 477="">>
but I can compile without debuging or I can debug it, and there is no problem; it works correctly:
what is it a problem at time opening exe file?
thanks for attention
|
|
|
|
|
Please do not create multiple accounts in order to post the same question twice.
Use the best guess
|
|
|
|
|
Possibly the worst sock puppetry act ever. 
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
How dense can you be? Its the value you are passing to the Qlist::[] opperator! Its telling you that it is too big!
Holy crap, I wish I had error messages this easy.
If you dont understand that accessing member 2909483625284948 of a 22 member array is a bad thing then go get another job.
|
|
|
|
|
f*** you Erudite_Eric 
Do you think that you are smart, but you're awfully stupid
|
|
|
|
|
Actually I know I am stupid, thats why I force myself to think very carefully about things.
|
|
|
|
|
Sometimes it's better to say nothing  .
|
|
|
|
|
Especialy without thinking first.....
|
|
|
|
|
Hello. I'm trying to open exe file , but there is a problem like this:
<<assert failure="" in="" qlist::operator[="" ]:="" "index="" out="" of="" range",="" file="" c:\qt\4.8.1\include\qtcore\..="" ..="" src="" corelib="" tools="" qlist.h,="" line="" 477="">>
but I can compile without debuging or I can debug it, and there is no problem; it works correctly:
what is it a problem at time opening exe file?
thanks for attention
|
|
|
|
|
Member 10072694 wrote: it works correctly:
Not if it gives "index out of range" error. You need to do some more debugging to identify where this error occurs in your code.
Use the best guess
|
|
|
|
|
Member 10072694 wrote: what is it a problem at time opening exe file?
Your code is trying to access an item of the QList providing an invalid index (possibly the index is bigger than QList size). As suggested you should debug your application to find out why this happens.
Veni, vidi, vici.
|
|
|
|
|
but at time debuging there is no problem, and my project works correctly
|
|
|
|
|
Mkhitar_Sargsyan wrote: but at time debuging there is no problem
That just means that the data you are using while debugging does not show the error. You need to reproduce exactly the same conditions that cause the error in order to find it.
Use the best guess
|
|
|
|
|
|
How would we know? It's your program so you are the one who understands it.
Use the best guess
|
|
|
|
|
yes I know it, but it strange that at time debugig there is no errors, I opened all list of errors, and there is nothing.
And my project with debug works correctly, it's strange that it's a problem at time opening exe file
|
|
|
|
|
Not strange at all; this is a fairly common occurrence. You need to add some code to the program to identify why this value goes out of range at some time.
Use the best guess
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
