Posts by jephthah

meh.

the internet died the day the number of .COM sites outnumbered the number of .EDU site.

i've already mourned and moved on.

"The Dude abides."

some bartenders make money hand over fist. most do not. and even the ones that do, its a cycle of boom and bust. the bad days more than offset the good days.

it's not a stable job. you dont see many men or women feeding housing and clothing their families by workign in a restaurant or bar. the ones that do have to support their families on this kind of job, they have it rough.

i waited tables through college, some fairly decent restaurants, and i think i know what i'm saying when i say waiters do not make the kind of money you people seem to think they do.

so, Jew, your figures don't reflect reality. here's why

(1) tables are not always filled. tables are often empty depending on night of the week, time of night, local economy, host(ess) playing favorites, all sorts of other reasons.

(2) tables do NOT turn themselves over every 15 or 20 minutes. i dont know where you go out to eat. Subway? McDonalds? People sit at their table for upwards of an hour or more, getting refills of iced tea or water all night long.

(3) people who have a clue, tip 20%. ignorant provincials, tightwads, jerks, old people, large groups of women, minorities, and all sorts of other people might tip anywhere from 0-10%.

(4) waiters tips do not go in their pocket. they have to "tip out" the hostesses, the bussers, the bartenders, …

There was a time when fgets did not exist. And people said, "gets works."

no, they said: "use getline()"

It works under certain conditions. It does not work under other conditions.

and those conditions are entirely impossible for the programmer to control. how much more broken does a randomly-exploding function have to be????

Well, as long as there are hackers [minimize, weasel, misdirect].

throw all the red herrings you want, but every computer security expert in the world understands the risk of buffer overflows, and recognizes broken functions like "gets" are the root cause. at the very least it can catastrophically crash the program without any warning. now stop suggesting that people use it, and stop pretending you know better than than the combined experience in the entire body of C programming literature.

look, just bow on out, and go back to BASIC. You seemed to do fairly well over there, and it's become painfully obvious that compiled languages are not your forte.

we've got enough problems to fix. new users break their code and come here for help. not to have it broken some more by someone they assume knows what they're talking about.

.

oh, well, you have an awesome command of the english language. i thought you were a native speaker.

i feel bad for you guys out there. a bunch of really good talent, sadly being instructed in an educational system that perpetuates incompetence in the administration.

I'm not embarrassed to admit that I haven't a clue about what you're talking. However, I do have Super Secret Investigative Powers, so i was able to find out:

CUDA (an acronym for Compute Unified Device Architecture) is a parallel computing architecture developed by NVIDIA. CUDA is the computing engine in NVIDIA graphics processing units or GPUs that is accessible to software developers through industry standard programming languages. Programmers use 'C for CUDA' (C with NVIDIA extensions), compiled through a PathScale Open64 C compiler, to code algorithms for execution on the GPU. CUDA architecture shares a range of computational interfaces with two competitors -the Khronos Group's Open Computing Language and Microsoft's DirectCompute. Third party wrappers are also available for Python, Fortran, Java and Matlab.

so i don't think youre going to get much help here. this is far too specific of a niche application. we generally don't deal with proprietary extensions. We can't, really. Questions about proprietary libraries are far better handled by people with expert knowledge in the specific libraries.

good luck

.

i'll take back my neg assumptions of your instruction/curriculum. i thought you were from the indian subcontinent, or southeast asia. because they apparently have entire universities that force students to use Turbo C for some unknown reason. since you're from a western country, your instruction is probably adequate.

yes, do uninstall that compiler. it is bad. There are many good options, including MSVC. I recommend the free Code::Blocks. download the windows version that comes with MinGW compiler, it's fully modern and adheres to industry standards.

as for "fgets" its from the same <stdio.h> library that "scanf" is in. there's no reason to think you're not advanced enough to use it. Check it out, .

good luck.

.

you found a rather interesting and little-understood tidbit in the scanf() function..

note the string has a space ' ' before the specifier: scanf(" %[^\n]",line); ... this is just as critical as the odd-looking format specifier.

from the IEEE Standard:

A directive composed of one or more white-space characters shall be executed by reading input until no more valid input can be read, or up to the first byte which is not a white-space character, which remains unread.

while the %[^\n] excludes newlines from the list of readable whitespace,... meaning that a newline will flush the input buffer and send all input to the character array.

it's kind of neat.

#include <stdio.h>

int main (void)
{
    char line[200];
    while(1)
    {
        printf("\nenter a string: ");
        fflush(stdout);         // safety flush since no newline in printf above
        scanf(" %[^\n]",line);  // note space character
        printf("you entered >%s<\n",line);
    }
    return 0;
}

you can try alternate builds where you remove either the single space, or the %[\n] and see what happens

i will say that, while it looks pretty cool, it appears that you can't protect buffer overruns, like you can with fgets...

i'll also admit i'm a little fuzzy on how exactly this directive is interpreted.

I'm aware of [ the problem with "gets" ]. But I just think that the user needed some simple help. But to get the user started, it helps to not get them bogged down in all the fine details.

i hear what you're saying, but sorry man, but you're totally wrong in this case.

there is sometimes value to keeping things simple.... For instance one could make an argument about using "rand() % 6" to roll a die, rather than getting "bogged down" in the finer points on the nature of pseudo-random generators.

but the ugliness of gets(), the pure incompetence behind using it, is beyond any considerations of simplicity. if there is ever one universally agreed upon rule in C programming, it's this: never. use. gets().

if you want to put a huge hole in your programs, no one will stop you, but shouldn't admit it in public, and absolutely never recommend it to new users who likely don't know any better.

the quick answer is that youve got unbuffered input due to your use of scanf()

but you've got a number of bad programming practices here, that i can't ignore. I suspect the blame is due to incompetent instructors teaching substandard curriculum on compilers that are 15 years out-of-date.

So I'm just going to lay it out, and if you choose not to take this advice ... well, at least I told you.

the non-standard <conio.h> library is obsolete. cease using it. this means that you will not be able to use things like "textcolor" which is unnecessary now that the days of DOS has been over for at least 10 years, and "clrscr" which is always obnoxious. you will not be able to use "getch" either, but don't worry the standard-C library <stdio.h> has "getchar" which will suffice. But you'll really want to use "fgets" anyhow, for most console input.

do not use "exit()" to quit a program due to normal events. this is a terrible practice, and will cause all sorts of problems once you start writing real programs that interface with real hardware and live databases.

steer away from using scanf(). the lure is tempting, but you need to learn to avoid it. its the source of many problems. fgets() will get a string safely that can be converted to numeric value and allows a relatively easy error-checking method to ensure the input buffer is cleared in case input is too long. (i'm …

do not make it global. that is not good advice, and doesnt fix the root of your problem.

i do agree that you need to use fgets(), instead of scanf(), because scanf() should never be used to input strings. scanf will not accept anything further once you pass in a whitespace.

your real problem here is that in your string size of 100 characters, everything beyond the end of the input string is garbage, and your reverse function is attempting to print all that garbage.

say you enter the string (using fgets!) that reads "hello how are you". this gives a string of length 18 characters: the 17 characters and spaces, plus the newline character. (note that you would need a char[] array of 19 to hold it because of the guaranteed terminating Null character.)

the remaining 81 characters is random garbage. you do not want to print those, you only want to print the first 17 characters that are valid.

do something like this in your "reverse()" function:

length = strlen(str);
    if (str[length-1] == '\n')
    {
        str[length-1] = '\0';
        length--;
    }
    for(i=length-1;i>=0;i--)
    {
        printf("%c",str[i]);
    }

Note: "strlen()" requires that you include the <string.h> library.

.

in your "count()" function within the body of the "for" loop, test if the character is a space ' '. if the character is a space, then break out of the for loop early by using the "break" command.

if you want to be thorough, test also for \newlines and \tabs

if (c == ' ' || c == '\n' || c == '\t')
   break;

finally, make a nominal effort to spell words correctly. you are not posting from a SMS texting cellphone, so typing "wut" and "wud" and "tat" and "wen" makes you look like a goddamn willful retard. If you do it anymore, i'm never going to help you again.

.

Please understand that Turbo, no matter how old
1) is in use
2) works
3) is not going to get replaced because you don't like it.

And stop regurgitating hatred for something you've go no business even commenting on. It's getting old.

"in use" ? really? where?? name for me a credible software company that uses Turbo C to develop meaningful, widely-distributed software for the commercial sector.

"it works" ... hey that's a good criteria ... an abacus works, too. perhaps we should teach business students how to balance ledgers with an abacus. and, by the way, don't let your definition of "Turbo C works" include crazy things like multithreading.

"wont get replaced because you don't like it"... hey, i'm a one-man army on a mission from god.

"stop regurgitating ... got no business ... getting old" how about we look through the past month or two of your posts and count the number of rants where you go off on people for using Turbo C. i'm noticing you have a pattern of harassing members for the exact same behavior you engage in yourself. :icon_rolleyes:

.

indeed.

there's always room for another 73-page thread of opinions on U.S. politics on the interwebs.

well, dammit, i wanted a joke. i guess if you're starting them without finishing, ill finish without starting!

redneck 1: "sure is cold."
redneck 2: "and deep, too."

i thought that was a good idea at first, but then I think about it for a moment, and i'm not so sure....

IMO, the few people who legitimately bump threads are newer users and they bump them b/c they misunderstand what was being discussed or the solution presented and are seeking clarification.

having a minimum post count would exclude the very people who are most likely be the few legitimate thread-bumpers in the first place.

it also imposes another layer of membership-status to segregate "probationary members" from the general population, as well requiring differentiating auto-closed threads from those closed due to specific abuse. That seems like a more substantial change to the site architecture.

an auto-close of all threads idle for more than 90 days would be easy to implement across the board. Moderators would have the ability to unlock a thread by request, per their discretion.

.

as part of a project I've got to conjure up a programme,

"Conjure a program" ... Interesting choice of words.

Rather viewing your exercise as needing to write a program, you see it as an attempt to magically produce one from the ether.

And begging and wheedling has replaced the ritual incantations of yore.

for the life of me, i do not understand why ;) is rendered the same as :P ... it is really annoying. i use :P alot, and i don't really use ;) very much except for certain occasions.

now, everyone thinks I'm a ;) kind of guy when i'm actually just your basic sort :P chap.

knowutimean? :P

.

yes, good points.

i know about that particular rand method being not the best psuedo-randomizer. And i use the preferred method which you cited in my own programs.

but i figured he was just taught this particular "easy" way, and he already has enough new concepts to get a handle on before addressing more esoteric aspects of pseudo-random number generators than would be addressed Programming 101.

and i'm not sure why i used float. a voice in the back of my head was asking me the same question.

life is just so HARD

i didnt copy and paste my assignment,i wrote the code by my self but in the end iam having problem

yeah right. is that like when you posted:

below u will find a incomplete code,try 2 complete the code.

...

/* PLACE YOUR CODE HERE */

LOL. your incomplete code, hmm?

how 'bout u try 2 lie a little better.

we're not as dumb as you look.

.

it's not a homework .

Liar.

you posted a file called "LabAssignment.doc" . Which wants you to use lame-ass <graphics.h> librayr, Turbo C style, to draw some basic pictures.

Sorry, but we're not as dumb as you look.

come on ,, no one want to help me

ya think???

that wont solve most of it. most thread hijacking occurs in current threads. And while this is annoying, it is easy to deal with. simply tell them to make their own thread and ignore them afterwards. the issue self resolves.

what's more of a problem is how every other dipshit comes along posting an "answer" to a thread that is 4 years old. Their answers invariably suck, and will wind up appearing to be a solution to other people who find the thread in their searches later.

The Powers-That-Be seem to think that by leaving threads open indefinitely we wont deprive ourselves of some gem that comes along at some unspecified later date.

But I have yet to see any time anyone ever contributed anything remotely meaningful to a thread that has been dead for more than three months.

Simple solution, after 3 months of inactivity, auto-lock the thread. allow such threads to be unlocked only by a specific request from a member. that way, they'll really have something meaningful to request a closed thread be reopened.

and i wont keep getting stupid emails telling me that someone's replied to a thread i havent even thought about in 2 years.

i dont normally work in the console/terminal window in my day job. so, i keep rewriting this every time i respond to someone needing help related to getting user input. im putting it here partly so i dont have to keep rewriting it.

this function will get a string input safely from the user and flush any extra characters if they enter too many.

if you (the programmer) need to get an integer or double floating point value from your program's user, then just follow up this code with a call to the strtol() or strtod() function from the standard C library, <stdlib.c>

this function forces the user who inputs the string to stay within boundaries, but just as importantly, it does not tempt the programmer (you) to use dangerous functions that could overflow buffers or get input "trapped", or to use undefined functions to try and flush the input buffer, etc.

And if your user does not input the correctly formatted value(s) that your program is looking for, strtol, strtod, etc. will point that out and allow you to handled invalid input gracefully.

@jephthah, thanks alot :)
but there is no such thing in my lesson how to give multiple values for IF

well, you were certainly trying to do so! but you were doing it wrong. IF takes one conditional statement. the statement may have one or more values. you need to be able to deal with ANDs and ORs in your conditional statement, as you can see by your need to find the condition when 'a' equals either 0 or 1. to try and do this with only one value at a time, would be ridiculous

@WaltP , Our teacher teaching us from the basic and they told us to use such functions, i don't know any other function to use then these void main(void) and clrscr () & getch () , can you tell me which functions should i use istead of the functions above ?

i wasn't going to bother correcting this, since you've got more fundamental problems... but since Walt brought it up:

(1) always use int main (void) ... you will need to add a return 0; at the end of your main block. "void main" is wrong. it's undefined and can cause all sorts of problems in larger projects. any instructor that tells his student to do so, is immediately suspect of incompetence.

(2) you should never use "clrscr()". it's entirely unnecessary and obnoxious.

(3) use getchar() instead of getch().

(4) stop using the conio.h library altogether. use stdio.h and stdlib.h …

you're trying to use a 20-year-old compiler on a modern OS. that's the problem.

Turbo C sucks enough already, but is known to be especially more problematic when installed on Windows Vista.

there are some workarounds but I'm not going to advocate them. The real solution starts when you uninstall Turbo C and throw all your copies away.

line 7 is the problem.

a=0 is an assignment. a==0 is a conditional statement. you need to understand the difference. also, you can't test multiple conditions by throwing a comma between values. you need to fully express each condition, separated by an AND (&&) or an OR (||) as the logic you're trying to acheive requires.

so, what you are trying to say in line 7 should be if (a == 0 || a == 1) this is fundamental stuff. you need to review your early lessons on IF statements, conditional and assignment operators.

We are forced to use turbo c at college

your college forces you to use a substandard compiler and IDE that is 20 years out-of-date, that uses deprecated and obsolete libraries, when modern industry-standard compilers and development environments are freely available in the form of GCC and MinGW.

think about that.

but i applaud you for trying to move to MSVC. you have the potential to break out of this cycle of despair. keep using MSVC whenever you can. if you dont have the full installation, consider checking out the full development CodeBlocks complete with modern graphics libraries and debugger.

it's totally due to that terrible hack of a "wait" routine. that's it and that's all.

the while loop is using every single available CPU cycle to approximate a timer. Like AD said, you need to use the library function for sleep(), in order to free up the CPU for other processes.

the other tweaks are good coding practice, but any speed gains won't even be noticeable compared to that behemoth of a cycle-eater you've got in that while() loop.

That's not pseudocode. That's BASIC. :icon_wink:

eh, i thought BASIC was pseudo code :P

glad to help.. sorry i got you diverted on the addition thing.

okay, sorry, you're right i'm not understanding your question. let me try again.

you're trying to calculate a factorial. in this example you're trying to calculate the factorial of "5". the factorial of 5 is

5! = 1 x 2 x 3 x 4 x 5 = 120.

your program performs this by a using a loop, by multiplying each of these numbers and holding the value in the variable "c". in your specific case, your program does it in reverse

5! = 5 x 4 x 3 x 2 x 1 = 120.

but its the same thing. in any event, please forget that i said anything about addition. you should not be using the addition operator "+" or "+=" for anything here.

here is what you have:

a = the number you want to take factorial of
b = a loop counter
c = the total answer, kept as a running value.

c is initialized to 1
c = 1

a is set to 5
a = 5

b is set to value of a, at the beginning of the "for" loop.
b = a

start loop using b, and decrement by 1 as long as b > 0

first loop:
b = 5
c = c * b
c = 1 * 5
c = 5

second loop:
b = 4
c = …

okay, hang on a sec. lets get the definition of 'factorial' agreed upon.

factorial is a total products, as calculated using recursive multiplication from 1 up to the number that you are getting the factorial of.

factorial of 5, is written as "5!"

and 5! = 1 x 2 x 3 x 4 x 5 = 120.

so you should be multiplying it as originally shown, using the "c *= b" assignment

(there is another operation that does addition, like 1 + 2 + 3 + 4 + 5 = 15, but that's not a factorial, i forget what it is called.)

so the whole point of this program is to be able to vary the number you want to compute the factorial of. in your example 5 is used, but there you should be able to check any number within a reasonable range, such as 6! or 7!, etc....

that's why you use a loop, because the point is not to just hard-code "1x2x3x4x5" ... but to be able to count any number of factorials from 1! through at least 12! depending on how large of an integer you can handle.

thanks alot :)
but here b is equal to 5 4 3 2 1 , then why ithis program is multiplying all the values of b ???
i mean why the ouput is 120 since we never said to the program to multiply all the values of loop

i don't know why you're multiplying it. you're the one who wrote the program, right? ;)

change the multiplication operator to an addition operator if you want to recursively add values c += b .

because your assignment statement c *= b; is a shorthand way of saying c = c * b by setting c=1, this correctly causes the first execution to be read as "c = 1 * b", and uses the value of c recursively each time afterward.

if you don't initialize c=1 at the very beginning, the first execution will be "c = <some_unknown_value> * b"... and you don't want that.

.

Funny thing, Walt, i've noticed your own recent posts where you do exactly the same thing.

such as this one here, where your only response to some guy's crap code was to tell him that it's full of problems and he needs to refrain from posting.

Please ignore yila's code. It is full of problems.

yila, please refrain from posting (supposedly) working code for people. They learn nothing so you are hurting more than helping. Especially when you use bad coding practices.

C Forum "Half Pyramid" thread post #8, March 07 2010

No explanation of why it was bad. Not even an explanation of *what* was wrong.

Now I wouldn't ever call you out on it because i totally agree with you. I'm tired of explaining the same things over and over to every noob and his brother. Crap code is crap code, and being nice and patient about it doesn't change the fact that most of them aren't listening anyhow except long enough to get the quickest and easiest answer.

And as for credibility ... that's a non issue. Veteran posters like yourself with thousands of posts and hundreds of "solved threads" don't NEED to establish credibility. At least not for newbie posters asking basic "why doesn't my program work?????" questions.

.

The ** was a typo

oh, i see. well, the double asterisk operator (**) is in some languages the "Power" operator. so that cubeVal = i ** 3 would be a valid expression for some languages, though not in C.

I forget where that's used, maybe in BASIC. that's what i thought you might be trying to do.

We're not allowed to use the math library as we haven't done it...

yeah, i figured as much. that's why i prefaced it with the future-conditional statement "in the real world you would _____"

it's common practice that beginning comp sci classes force you to do things the "long" way so you understand the mechanics before they let you take off and use standard libraries.

anywho, if you follow my pseudo code, you should have this done in no time.

.

well it works

that's what Toyota said about their millions of recalled cars.

but still, i'd like you to tell me what's wrong with it.

here's why your code is bad. (in your defense, i will say i have seen more bad code crammed into such a short space.)

(1) void main()

(2) printing console instructions prior to a user input without flushing the output buffer either with a \newline or a fflush(stdout) call

(3) using scanf() to get user input from the console.

all of these are basic examples of bad coding that causes no end of real-world program failures. This has been explained here and elsewhere ad nausuem, and i am not going to spoonfeed you answers to questions that have been addressed hundreds of times. If you really want to know why, look it up

seriously, guys, this forum is not what it is used to be.

lol, really, in all your 9 months and 17 posts? you crusty old veteran, you.

on y!answers, you actually happen to find some guys with knowledge, but here i am utterly disappointed

well, as my grandpa always said, "Don't let the door hit you in the ass on your way out."

.

drewangel : i am using turbo c++ compiler and including the header file pthread.h , but i am getting error and it is not getting included

AncientDragon : Your compiler does not support threads. You will have to use a modern compiler '

drewangel : thanks for your reply. but i want to know the synatx for pthreads. are we supposed to use pointer to functions in that?

my goodness. Reading comprehension, much?

Turbo C does not support multithreading. you will not get a POSIX thread library to work. What part of this are you not able to understand?

.

wait, wait...

your code prints a full pyramid.

3=   *
    ***
   *****

which is way more complicated than printing a half pyramid.

3= *
   **
   ***

man, how did you figure out a full pyramid but not be able to get the much simpler half pyramid?

read what walt said. that's the answer, it doesnt get any simpler.

@nezachem : nobody cares which martial arts you claim to study. "grasshopper" is a frequent term applied to a new learner in any subject. thats it. if you dont understand english language colloquialisms, move along and don't waste time requiring someone to explain trivial shit.

as for this piece of "advice"

Start simple. Create a server, which holds a [blah blah blah ... snip]

do you really think that someone who cant even begin coding on a simple game program partly because they don't understand the common architecture of their unix system, is going to build a server? he cant use sockets anyhow.

@iliali : look, 90% of this becomes relatively simple, if you back up and quit trying to look at this a whole problem. look at it as a series of little problems.

you need to do the following one step at a time.

(1) build an array to hold a map
(2) build structure(s) to define elements of what that map contains.
(3) define an interface to "move" a "piece" around on that map,
(4) keep track of where the piece is in your structure
(5) ensure that your "piece" cant move illegally based on locations of other objects.

move through this incrementally. build a little bit, test it. Build a little bit more, test it. integrate these two things, test it. and so on.

(6) then you add in a second player, and modify …

crappy (krap' e)

- adjective, slang.

(1) difficult to implement without requiring an excessive amount of overhead to prevent it from falling apart during normal field use.

(2) anything that exists alongside a freely available alternative from the standard library that covers most use scenarios in a manner resistant to typical input errors and with a minimal of overhead.

(3) any function that is routinely handed to noob programmers who don't grasp its complexities, who invariably use it to write poor programs and then stream through programming forums in a non-stop "why doesn't my program work" parade.

(4) the state of being crappy.

(5) scanf()

.

n is XOR'ed with an unsigned -1, the resulting value is stored in 'n'

-1 is treated as an unsigned integer, meaning just that it's a variable with all bits are ones. a 32-bit int, will be 0xFFFFFFFF

basically this is like a microcontroller register operation that "flips" all the bits in a register.

i.e., the value 0xA5A5A5A5 when XORed with 0xFFFFFFFF becomes 0x5A5A5A5A

OMG

It was a stupide question

Thank you for answering! ;)

i recall some recent snafu at NASA causing a significant failure, and being traced to a divide-by-zero error. (or, maybe i dreamed it. i'm not sure now...) but anyhow it's not a stupid question. it's a good lesson.

For instance, I just had to come into work all day sunday to revalidate a production system revision that failed because I had accidentally inserted a single "stupid semicolon" immediately after a FOR conditional statement.

point is, everyone needs to check their work, because these "stupid errors" can get by any of us. your learning now, will save you time and money in the future.

.

i'm still saying that overwriting the original string with \newline characters is a bad idea. it makes the program unnecessarily complicated, and opens up more opportunities for buggy code.

I suggest that you reconsider your approach to the problem. to put it one way, i think you are "going around your ass to get to your elbow". nothing personal, its a problem all new programmers (and some old) have.

consider this: simply break your string into tokens that are already delimited by the existing spaces. then, concatenate all IP addresses (with or without their trailing commas) into one string.

const char str = "/usr/bin/ssh * 147.188.195.15, 147.188.193.15, 147.188.193.16 22";

char PathName[MAXPATHSIZE] = '\0';
char UID[MAXUIDSIZE] = '\0';
char IPaddr[MAXIPADDRSIZE] = '\0';
char Port[MAXPORTSIZE] = '\0';

char *ptr;

ptr = strtok(str," ");
while (ptr != NULL)
{
   if (strstr( ptr, "/") != 0)
      strcpy (PathName, ptr);
   else if (strstr( ptr, ".") != 0)
      strcat (IPaddr, ptr);
   else if (strstr( ptr, "*") != 0)
      strcpy (UID, ptr);

   /*
   ...  now you figure out how to distinguish between numeric UIDs 
   ...  and numeric Port Numbers
   ...  One possibility is a "state machine" or just a flag that tracks when 
   ...  the IPaddresses have been found, so a subsequent
   ...  simple numeric must be a Port and not a UID.
   ...*/

   ptr = strtok(NULL, " ");
}

.

once you address what walt said, your first code problem i see is <conio.h>

remove that line, and remove everything that depends on it. then rewrite in standard C.

until you do that, i doubt anyone here will bother trying to compile and run your code, because no one uses the joke of a shitty compiler that continues to use that deprecated library.

hi....... I want a program in c based on any data structures with de code.plz............it shd be catchy n can be based on reality

omfg U R 2 cool! wer R U @ a/s/l? Did U gt de CODEZ? snd dem 2 me PLZ! zomgWTFbbq!!!1 lololol

.

what is the function that can be used to count the number of days that a thread has been dead and buried?

I know this is using C. But if i was using the stdlib.h to use C in C++ ..... trying to find a simple way to add two hex numbers together but in C++;

I know this is the C forum, but if it were the C++ forum, it would be a different forum.

I also know this thread is 1-1/2 years old, but if it were a new thread, it would be a different thread.

your question doesnt make any sense.

and we dont just hand out solutions to every beggar that comes along, anyhow.

why don't you just use the security settings built into IE to whitelist/blacklist websites? reinventing the wheel is usually a waste of time, especially when you obviously don't know what you're doing.