globals are widely considered poor programming. you should learn to not use them, by not using them unless you have a condition where it's necessary to do so.
You think "it works" for you now, but it's a Faustian bargain. And it will come back to haunt you.
Something I've never understood. If you have something wrong with you, US films/tv show a demand for a credit card when the hapless individual is rushed into ER.
What happens if somebody is rushed into ER, is treated for something really serious (e.g. heart attack), but it is then found that they do not have medical insurance? Do they then get fleeced by sharks and are forced to sell all their worldly goods or are they simply thrown out on the sidewalk?
OR, if they are treated anyway, why bother with medical insurance?
Totally perplexed.
no, they just get your ID info and do the insurance paperwork later. if you dont have insurance you get billed. if you don't pay your bill, it just sits on your credit record and negatively impacts your ability to get unsecured loans. if you don't pay bills, then generally you probably dont care about your credit record anyhow.
non-private hospitals and regional trauma centers become the primary care for people with no insurance, becasue they do not turn away patients who need medical care. since these millions of people without insurance are clogging up the trauma center ERs, they drive up costs for everyone else, and consume resources of ER centers that cost probably 4-10 times more than a primary care provider.
it makes no sense to continue such a system. if people can get primary care at a regular provider and deal with health maintenance in a reasonable way …
If waiting tables is truly slave labour, shouldn't you ... demand a decent (minimum?) wage. ... tipping could then be abolished. ... in the UK/other parts of Europe ...
speaking of "Leaders" and being incapable of "independent thought" do you get your rants from Glenn Beck or Rush Limbaugh, or do you just synthesize Fox News talking points in general?
you'd have to get rid of the "type ahead input" from your terminal, which is controlled by the operating system.
the answer on how to do that in standard C, is you can't. there are some old DOS libraries out there that can, and there's a POSIX library for Unix, but it's dependent upon finagling with the operating system, and it's not standard C.
here in the 21st century, entering and hiding passwords is handled in GUI applications via callbacks.
8-bit ASCII characters include a lot of non-printable and extended characters that are difficult to transmit properly between certain applications.
"Base64" is just a conversion method that changes a string of ASCII (printable and unprintable) codes into 64 different "clean" (printable) characters... (Note: since ASCII value range from 0-255, in this context it could be considered as "Base256".)
to reduce an ASCII string down to 64 printable characters, a string of 8-bit ASCII characters are converted to a string of 6-bit Base64 characters. the 64 characters used are typically [A-Za-z+/].
every three (3) 8-bit ASCII characters convert to four (4) 6-bit Base64 characters (3 chars x 8 bits = 4 chars x 6 bits). to ensure the converted string length is a multiple of 4 characters, one or two equal signs '=' may be used to pad the end of the last quartet if needed.
the "encryption" you're thinking about is that OpenPGP encryption uses a form of Base64 for transmission called "Radix-64" -- also commonly referred to as "ASCII-armored" text -- which includes a CRC checksum to ensure transmission didnt mangle any data.
But Base64 is not an encryption, any more than ASCII codes are "encrypted". It's just a conversion used as part of the transmission protocol for applications including some encryption processes.
when you declare a prototype, like in line 4, you declare the function type, function name, and argument types, like you did: void printtable(int x); , this must match the definition of the function, which you have down on line 46.
but when you *call* the function in the program, like at line 9, do not include the function type or argument types, so you just call it like so: printtable(10); .... where the number "10" (for example) could be any "int" value and will be passed to the function.
when you get to the function definition, starting at line 46:
void printtable(int x) /* Function definition */
{
for (x=0; x<10; x++)
{
printf("%d",x);
printf("n");
}
}
you see that whatever value passed in from the function call (line 9) will come into this function via the argument as "int x"... the purpose of this would be to have a value that could then be used for whatever purpose you intended within the function.
HOWEVER, what you are doing is not really correct, or at least is not what is intended. once you get to the function, you reassign "x=0" in your FOR loop, thereby losing whatever value was passed in.
it seems to me that you really intend to have "x" be the upper limit of your for loop, so that it counts out "x" numbers. change your printtable function to something like this:
void printtable(int x) /* Function definition */
{ …
I'm not convinced that's correct. i'm not even convinced the indentions that have appeared since Walt added the code-tags are correct. they're pretty much a mess too.
i'm half suspecting the print() and printtable() are really the same function that was just misnamed in one spot.
we won't really know anything until the OP returns to clean up his code.
the Python forums are fairly popular here. I dont know anything about semantic technology. best if you popped in over there and gave them a holler, i'm sure they'll help you as they can :)
I was born in Okinawa. Aza-Kuwae Chatan-Son, if i correctly recall what's written on my birth certificate. I often wonder about my birthplace, i was only 3 mos old when my folks brought me back to the States. (my dad was USAF). he was there for a year and has good memories of the island, the people and scuba diving.
And if the dam breaks open many years too soon And if there is no room upon the hill And if your head explodes with dark forebodings too I'll see you on the dark side of the moon.
I too am having a hard time understanding what you're asking.
are you saying that you want the lines to be printed "n" number of characters wide, such that extra spaces are inserted between words in order that both the left- and right-hand sides are justified margins?
Example: n=12 Sentence = "Now is the time for all good men to come to the aid of their country."
Result:
Now is the
time for all
good men to
come to the
aid of their
country.
Schildt is smarter than me too, but he's been criticized relentlessly by a number of people on the ISO standardizing committee. They seem to particularly revile his Annotated C Standard but also are quick to disdain his C: A complete Reference
I have C:ARM somewhere. i never had any problem with it as a generic learning guide/reference, other than it was a bit simplistic and sparse.
The fact that it happens to work on some environments (your Unix) but not others (your Mmac) doesn't mean that Mac is the problem. Mac is working correctly. your CODE is wrong.
as what thomas noticed, above, your array sizes are not defined correctly.
char letters[[B]6[/B]];
int mem[[B]3[/B]];
must be changed to
char letters[[B]7[/B]];
int mem[[B]4[/B]];
if you leave it the other way, even if it happens to work on some particular platform, the code is still wrong.
I was always brought up that cow tipping was a standard rural recreation event. So it was surprising when my mom argued with me today that it is now considered rude to suggest that provincials will engage in an evening of cow tipping. I have nothing against cow tipping, but to me it seems a bit unpleasant for the cow and possibly dangerous. Since cow tipping is apparently so widespread I don't see any logic behind this supposed change in attitudes about it. Being an urbanite I might be out of the loop. Maybe it's just a hoax. Thoughts?
void print(int x) should not also have a local redeclaration of "int x" choose either one or the other. what is this doing, anyhow? printing 1-10? why do you need a dedicated function to do that?
good lord this is a mess.
where does your main() routine even end? where do your function definitions begin? are your functions "printtable" and "print" the same functions?
clean up this mess of code and repost it using proper indentations and code tags, so we can see what the heck is going on.
EDIT : oops, i didnt realize this this thread was 5 days old.
nothing wrong with 70%.... heavy reads in a while loop,that would be expected. if other programs need (or are already using) cpu resources while this program is running, they will share the available resources.
and yes, get rid of the bzero. it's unnecessary. the fgets will null terminate the buffer after each read.
i'm afraid that if the Birchers and Teabaggers find out i'm a card-carrying pinko batshit liberal pantywaist, they will stop giving me positive rep in the C forums.
yeah, i understand the problem of the retirees with fixed income and medical bills. so i always cheerfully waited on them just the same, expecting to get a small tip, and would be graceful to receive it because i figured they were doing what they could.
but there are some older folks who just have this attitude that tipping is some sort of communist plot or something, and they just flatly refuse to tip.
either way, the probability is against the server when waiting on older folks. it's just the way it is. i'm glad you're able and willing to tip appropriately as the service deserves it.
DISCLAIMER: i'm not ever suggesting that anyone should reward truly bad service, or give a full tip for subpar service. but do consider that sometimes things are out of the server's control, and it's not an easy job.
