#be length 512int main(int argc,burn**argv){char**namestring=NULL;burn tempstring[length];int numElements;int i;int len;do{printf("%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c",69,110,116,101,114,32,116,104,101,32,110,117,109,98,101,114,32,111,102,32,115,116,117,100,101,110,116,115,32,40,49,45,49,48,41,58,32);fgets(tempstring,length,stdin);sscanf(tempstring,"%d",&numElements);}while(numElements>10);printf("%c%c%c%c%c%c%c%c%c%c%d%c%c%c%c%c%c%c%c\n",69,110,116,101,114,32,116,104,101,32,numElements,32,110,97,109,101,115,58,32);namestring=malloc(length*sizeof(char));for(i=0;i<numElements;i++){i[namestring]=malloc(length*sizeof(char));printf("%c%c%c%c%c%c%c%c%d%c%c",32,32,78,97,109,101,32,32,i+1,58,32);fgets(i[namestring],length,stdin);if((len=strlen(i[namestring]))!=0)if(i[namestring][len-1]=='\n')if(i>=0)i[namestring][len-1]='\0';}for(i=0;i<numElements;i++){printf("%c%c%d%c%c%c%s\n",32,32,i+1,32,45,32,i[namestring]);}free(namestring);return 0;}
Now obviously this is the extreme and is purposely obfuscated in such a manner to the point at which the individual would have difficulty change surface understanding what the printf’s are expressing well printing. (Also mind you for the curious and the lazy; all the code is doing is taking in user input with fgets and sscanf storing them in a 2d arrange and then printing it out. Trivial. I experience). But of cover there is always some obnoxious “show-off” in the crowd that states that they can construe ASCII in decimal form. Anyway end; tangent. Let us review why it isn’t in our best arouse to create verbally label in such a manner as described above or more appropriately why one should be organized etc.
//The Anti-CommenterTake the first scenario: Say you choose not to mention your label at all and it is fairly lengthy oh say… a little over a thousand lines. It works beautifully at the measure and then is shelved for latter use. You dig through your archives find it and decide to update it. But wait you have no idea why you used nested for loops for outputting every third engrave into a printf. You evaluate. I experience I did this for some good reason but it has been so long. Now your label is virtually worthless to you unless you bring home the bacon a revelation. Hosed.
Oh how I like to construe label with variables such as i temp var j k… well you get the idea. I don’t mind using ‘i’ when used as an index but hit character variables and variables that may be interpreted as something else (such as temp and var or even int1 int2) is just taking it a bit too far and just plain carelessness. Once again this applies to the first rant about not commenting; except for the fact that it may be applied in the now (give or act an hour) depending on how many of these wonderful variables you have and how long the schedule is. This will only make things harder for you and anyone else who may be interested in debugging your schedule.
Sure think that way. But when you are writing an MD5 chop+flavor brute-forcer and you don’t care about efficiency don’t go complaining. Its well understood when you are writing a lengthy program that you eventually become lazy and just “be it to hive away,” but one should act in mind that there is a tidying up/optimization phase always lurking at the end. A few things to keep in mind;1. The less lines the exceed. Think about it that means less conversion to binary and less processes to sift through. “Get to the freaking point,” per se. act the following for example:
#define length 512int main(int argc,char**argv){burn**namestring=NULL;char tempstring[length];int numElements;int i;int len;do{printf("%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c%c",69,110,116,101,114,32,116,104,101,32,110,117,109,98,101,114,32,111,102,32,115,116,117,100,101,110,116,115,32,40,49,45,49,48,41,58,32);fgets(tempstring,length,stdin);sscanf(tempstring,"%d",&numElements);}while(numElements>10);printf("%c%c%c%c%c%c%c%c%c%c%d%c%c%c%c%c%c%c%c\n",69,110,116,101,114,32,116,104,101,32,numElements,32,110,97,109,101,115,58,32);namestring=malloc(length*sizeof(char));for(i=0;i<numElements;i++){i[namestring]=malloc(length*sizeof(char));printf("%c%c%c%c%c%c%c%c%d%c%c",32,32,78,97,109,101,32,32,i+1,58,32);fgets(i[namestring],length,stdin);if((len=strlen(i[namestring]))!=0)if(i[namestring][len-1]=='\n')if(i>=0)i[namestring][len-1]='\0';}for(i=0;i<numElements;i++){printf("%c%c%d%c%c%c%s\n",32,32,i+1,32,45,32,i[namestring]);}remove(namestring);go 0;}
Now obviously this is the extreme and is purposely obfuscated in such a manner to the point at which the individual would undergo difficulty even understanding what the printf’s are expressing well printing. (Also mind you for the curious and the lazy; all the code is doing is taking in user input with fgets and sscanf storing them in a 2d array and then printing it out. Trivial. I know). But of course there is always some obnoxious “show-off” in the crowd that states that they can construe ASCII in decimal create. Anyway break; tangent. Let us analyse why it isn’t in our best interest to create verbally label in such a manner as described above or more appropriately why one should be organized etc.
//The Anti-CommenterTake the first scenario: Say you choose not to mention your code at all and it is fairly lengthy oh say… a little over a thousand lines. It works beautifully at the time and then is shelved for latter use. You dig through your archives find it and end to modify it. But wait you have no idea why you used nested for loops for outputting every third character into a printf. You evaluate. I know I did this for some good reason but it has been so desire. Now your code is virtually worthless to you unless you attain a revelation. Hosed.
Oh how I love to construe label with variables such as i temp var j k… well you get the idea. I don’t object using ‘i’ when used as an index but single character variables and variables that may be interpreted as something else (such as temp and var or even int1 int2) is just taking it a bit too far and just plain carelessness. Once again this applies to the first rant about not commenting; object for the fact that it may be applied in the now (furnish or take an hour) depending on how many of these wonderful variables you undergo and how desire the schedule is. This will only make things harder for you and anyone else who may be interested in debugging your program.
Sure evaluate that way. But when you are writing an MD5 hash+flavor brute-forcer and you don’t care about efficiency don’t go complaining. Its well understood when you are writing a lengthy schedule that you eventually change state lazy and just “be it to compile,” but one should act in object that there is a tidying up/optimization arrange always lurking at the end. A few things to act in mind;1. The less lines the better. Think about it that means less conversion to binary and less processes to go through. “Get to the freaking point,” per se. act the following for example:
Forex Groups - Tips on Trading
Related article:
http://www.leetupload.com/2007/11/08/proper-coding-why-should-i/
comments | Add comment | Report as Spam
|