Posts by Narue

Yes. To return a vector of strings, for example, you would do this:

vector<string> function();

To return a pointer to a vector of strings, you would do this:

vector<string> *function();

To return a vector of any valid type, you would do something like this:

template <typename T>
vector<T> function();

You can also return a pointer to a vector of any type. Templates are pretty versatile.

>what u mean with odd choice of advantages?
Data security isn't often paired with the scope and linkage of your variables.

>my lecturer told me local variable is better than global hence increase data security
That's an odd choice of advantages. Most people say that global variables are bad because they increase coupling between functions, make reuse harder, cause problems with multithreading, make the code harder to follow in general because you don't know where a variable is used, and make code harder to maintain because you could accidentally modify or hide the global variable.

Though I suppose your lecturer was using the versatile word "security" to mean the last three reasons that I listed. He doesn't sound like a very good lecturer if vague words with innumerable interpretations are his preference.

Play around with this and see what you can come up with:

#include <iostream>

using namespace std;

#define bit(x) (1UL << (x))

int main()
{
  unsigned int x = 0;

  x = 1; // 00000001
  cout<< x <<endl;
  x |= bit(1) | 1; // 00000011
  cout<< x <<endl;
  x |= bit(2) | 1; // 00000111
  cout<< x <<endl;

  // Get back a sliver
  cout<< (x >> 1) <<endl; // 00000011
  cout<< (x >> 2 << 2) <<endl; 00000100
}

>Why are the standard header files in C++ so non-standard?
They are standard and well defined.

>Particularly iostream seems to be the most dialectal.
Any compiler is allowed to provide non-standard extensions. Any issues you have with extensions are your problem.

This doesn't sound like a programming or software design issue. You didn't even bother to mention what browser you use. They're all different you know. Since you're somewhat clueless, I'll assume Internet Explorer. Go to Tools, then Internet Options, then Clear History.

>Basically i need to set on my computer so no one can see anything i have
>searched for or sites i have visited
You could stop searching for porn at work.

>if you then just press enter at the character search prompt you will find the \n.
That's reasonable (and expected) behavior. Let's say you want to test for exceptionally long lines:

while (fgets(buffer, sizeof buffer, stdin) != NULL && !check(buffer, '\n')) {
  /* Append buffer to a dynamic string */
}

If you don't want to find the newline, then remove it before the test, or verify the value of the search character as being neither EOF nor '\n'.

>Spend some time with your editor to look at the iostream header.
Spend some time with the C++ standard. iostream isn't required to include cstdio or stdio.h, so your code exhibits undefined behavior.

>The one that comes with Dev-C++
Not everyone uses Dev-C++.

Cover the bases for C++: Get "The C++ Programming Language" and go through it. If you're reasonably comfortable with most of what it covers, then you're okay. If you're lost for the better part of any chapter, you're probably not okay.

Do the same with Java. The language is very simple, so you can cover that quickly. The trick to programming efficiently with Java is knowing the "standard" library of classes. You can go to java.sun.com and look through their extensive documentation to deepen your understanding of the library.

Beyond that it's all practice. Read code, write code, and experiment as much as you can.

>So where is the error in my analysis?
The part where you relied on undefined behavior to do something predictable. I can't figure out if you're really as dense as you seem, or just stubborn.

>C99, C89, or C whatever are suggestions for compiler writers and they don't tell you what any compiler does.
They tell you what any compiler that claims to implement C must do.

>But my compiler (bcc32) doesn't tag it as a syntax error, so why should I care that C99 does?
Well, since that compiler doesn't implement C99, you should care because it's undefined behavior.

>This certainly doesn't make the computation incorrect. It's the compiler that I have to satisfy, not C99.
So you plan on using the same compiler for the rest of your life? What a narrow perspective you have. I pity you.

>works, even when there's undefined behavior
It could work, or it could wipe your hard drive. I personally couldn't care less what happens to your stupid ass, but I do care about you touting that code as "good" on this forum.

>Do you know which header file?
limits.h

><snip awful code and incorrect analysis> I hope this settles the matter.
Yes, it proves conclusively that you're an arrogant, ignorant retard who has no hope of becoming anything more than a mediocre script kiddie.

Reality check: Not everyone uses your compiler, your operating system, and your exact hardware configuration. When you realize this, you may actually have a chance of growing a brain.

>I have set a goal of 6 months to do best learning c++ and java
So in 6 months you expect to learn both C++ and Java to the point where you could use them professionally? Answer me this: What experience with programming do you already have?

>Gosh, I thought it was rather neat.
Neat is not the same as good.

>But maybe this bit of code will be more acceptable.
Not really:

>main()
main returns an int. For C89, it's okay (but poor style) to omit the return value, for C99 it's a syntax error. The correct definition of main is:

int main(void)

>printf("%d\n",sizeof(int));
sizeof evaluates to a size_t value, which is not representable as a signed integer (which %d expects). Under C89 you can get around this by casting the result of sizeof to unsigned long, and using %lu:

printf("%lu\n", (unsigned long int)sizeof(int));

In C99, the z modifier lets you print a size_t:

printf("%zd\n", sizeof(int));

>}
If you were using C99 then this would be legal because main returns 0 by default. However, because you're not using C99 (see above) it's undefined behavior because you neglected to return a value.

>Can anyone point me the direction of getting a linux verision that comes with a .cpp compiler?
g++ comes standard with every Linux distro I know of.

>but the compliler that I am using came with the software for the C# class.
Then remove the call to ReadKey and everything will work. That was the only 2.0 language feature that I used. There's a lot to be said for experimentation, you know. Check my blogs for a thorough rant on the topic.

Okay, what's your exact problem? I've already been kind enough not only to refrain from flaming you for posting in the wrong forum, but also to give you a viable solution to your last problem. I don't have a great deal of patience, so I highly recommend moving your thread to the .NET C# forum and asking a smart question. When I lose my patience, it's not pretty.

>there's a difference between C89 and C99 standards
Yes, there is. But you're missing the point.

>There's a subtle difference between these two terms.
There's also a subtle difference between the rules for integer literal conversions (that we've focused on for most of this thread) and signed integer overflow (displayed in murschech's horrid code). Signed integer overflow is always undefined, pick whatever C or C++ standard you want.

>What is this telling us?
It's telling us that you're struggling with simple concepts like "anything could happen".

i think u should grow up dude....do u think urs is the best english......dont do that mistake.....
what the hell do u think of u.........learn to talk........
i bet my english is a better one than urs.......u better stop this shit here.....

You're too funny. :mrgreen: *sigh* You're not even worth my effort, and I've taken the time to chat rape some pretty pathetic losers. Please enjoy the following sound. I'm sure you'll get it often.

*plonk*

>I asked 4 C and/or C++.......
Well, you should have said that, shouldn't you?

>I pity u for not even understanding that small thing
I don't need the pity of a person who butchers the English language. Don't talk about understanding until you can communicate effectively.

>come down.....
Grow up.

>gimme
I hate this word.

>C/C++
What is this C/C++ language you speak of? There's no such thing as C/C++. There's C and there's C++, but no C/C++, as any knowledgeable user of both will gladly tell you.

Anyway, to answer your pseudo-question/demand, go here: Thinking in C++

>This way you can 'int' everything in one line.
You can "declare" everything with the same type on one line. The wording you used is potentially confusing. Also, while vertical space is abundant, horizontal space is more valuable. Learn to use it wisely. For example, it's widely accepted that single line declarations should consist of closely related variables, if they're used at all.

In this case, an array would be better than any measure of formatting of multiple variables.

>but that wasn't what I needed
Maybe I'm just bitter, but don't you think it's trivial to take what Dave showed you and derive this to get what you want?

int k = 1;
for (int i = 0; i < 10; i++) {
  for (int j = 0; j < 10; j++)
    array[i][j] = k++;
}

Then you can even use the same trick to print:

#include <iomanip> // For setw

for (int i = 0; i < 10; i++) {
  for (int j = 0; j < 10; j++)
    cout<< setw(5) << aray[i][j];
  cout<<endl;
}

Or are you completely helpless? If you are then I suggest you quit right now. Helpless people don't last long as programmers.

>to demonstrate a char array overflow.
Array overflow is undefined. Your demonstration is non-sensical because the result could be anything.

>Now, is there anyone who can help me without being a fool?
Foolishness begets foolishness. Post some code and we'll help you with it. That's far more effective than asking a vague question and leaving the answer open to interpretation.

>Are you native Japanese (or 'Nihongo' if you feel more comfortable with)?
I think you meant nihonjin. nihongo is the Japanese language, not a Japanese person. If you really did mean the Japanese language then your English grammar bites.

Remove the int from in front of rtotal. Type names are (for the most part) only used in declarations and type casts. Because your use is neither of those, it's a syntax error. Of course, the code you've posted has other syntax errors as well.

The dynamic declination flag was accidentally switched to EIEIO. Check your atomic memory pool for floaters because they're probably causing the kernel to pop. But be careful because the memory manager is volatile and could cause the entire pipeline to dump core.

><iostream.h> is deprecated
No, it isn't. A deprecated feature has to have been a part of the standard in the first place. <iostream.h> was never a standard header.

>With iostream you need to put std:: before cin and cout.
There are three options for qualifying a namespace. First, you can qualify each use of a name by prefixing it with std::. Second, you can qualify all uses of a single name by saying using std::<name>;. And last, you can qualify all uses of every name in the std namespace by saying using namespace std;.

>Yes i'm compiling it as an .exe and it it runs fine.
That doesn't answer the question. When you create a project in Dev-C++ you can choose a Win32 application or a Console application. You chose a console application, which automatically spawns a command prompt window for running the program. A Win32 application does not.

>there're gotta be a better way ...
There isn't unless your system supports record-oriented files. Any solution will be a variation of what you were thinking of doing. Though naturally, any decent solution will take advantage of block reads and caching to avoid the performance hit of constantly reading and writing to disk.

vegaseat's suggestion is a good one for smaller files, but when working with multi-megabyte/gigabyte files, it's not practical to keep the entire file in memory at once. How you go about solving the problem depends on what files you expect and what kind of performance you're looking for.

>I keep hearing that Python is about as slow as Java.
Java can be comparable in speed to C++ or as slow as Christmas. It's not a good measure.

>Does anybody have experience with speeding things up?
Are you having problems with performance? If not, why bother? In my experience with Python, speed is rarely an issue if you actually bother to do things intelligently. Any moron can write code, but it takes work to write good code, and experience on top of that to write great code.

>There is a forth tutorial there for those that want to read about it.
I wouldn't recommend it. Try this instead. Nor would I or any other Forth users call it a "hacker's language". You're just an ignorant fool.

>do scroll to the bottom part on the C language part
I'm not even going to dignify your idiocy with a response. Clearly you're now not even trying to continue a reasonable debate, you're just sniping at us personally and everything that isn't Java. Go away, troll.

>This coming from a card carrying java hater is a real surprise.
What? It's a surprise that I hate a language yet still use it and recommend it? I'm not so foolish as to be unable to look past my own opinions, unlike some people I won't name.

>You guys should really read Narue's blog on java.
You should stop ignoring things that don't fit into your own conclusions. If you read all of my blogs, you'll see that I don't have as much of a problem with the latest version of Java. A lot of the non-fundamental issues were addressed, and that pleases me. But you wouldn't understand because you've already tagged me as a person like yourself that doesn't have an open mind and never changes their opinion in light of new information.

>Narue you also said "I'm sorry, I handn't realized that was a requirement" referring to forth
I wasn't referring to Forth. Try reading for comprehension sometime.

>As for Forth it is also known as the hacker's language. <snip silly comments>
Odd, I've been in the Forth community for some time now and I have yet to hear that. Maybe you're just trying to fake your way out of not knowing something.

>let me let me advice you guys not to be jack of all trades and master of none
Yet another wonderful suggestion from the woefully misinformed. There's no point in arguing why this recommendation is …

>None of those languages except Forth existed when I learned to program.
I'm sorry, I handn't realized that was a requirement. :rolleyes: I didn't list any of yours because I didn't find them particularly interesting, with the exception of Lisp and its derivatives.

>And NOW we have you Narue.
No, you just think you do because you're making the same mistake.

>IF ASCII is explicitly referred to it will ALWAYS be the same
Yes.

>because ASCII is a well defined set of characters and codes.
Yes.

>It stands for American Standard Code for Information Interchange.
Yes.

>If Any other character set is referred to you're theoretically correct
C++ doesn't define the integral values of the basic character set, so saying that 'a' is equivalent to 97 is wrong. Even if you qualify that as the ASCII value 97, it's still wrong because the C++ uses the native character set of the machine on which it's running. If the machine uses another character set, such as EBCDIC, 'a' certainly won't be ASCII, nor will its integral value be 97. So your argument falls flat.

When the OP makes it very clear that their character set is ASCII, I don't have a problem. But this is a case of making an unwarranted assumption (no matter how likely it may be) out of either laziness or ignorance.

To summarize: Even though ASCII is a well defined and standardized character set, it's not the only one out there. C++ caters to everyone, so assuming that everyone uses ASCII will bite you eventually.

>study java or continue my MFC????????????????????
Both. The more, the merrier.

>I was told to learn VB first, and then C++.
Learn whatever looks most interesting to you. If somebody tells you to learn a language and you hate it then you've just sold yourself short. VB is recommended because it's easy and powerful at the same time. C++ is recommended because it's incredibly flexible. Java is recommended because it's not as intense as C++. Here are a few of the languages that I've found interesting, at the very least:

C, C++, Java, C#, VB, Perl, Python, Forth

This might give you a start for research before you pick a language to focus on. Each of these is useful, popular, and different enough from any of the others to give you a new flavor of programming.

I never recommend C, C++, Java, or C# as a first language. They're meant to be used by real programmers solving real problems. As such, they're awful as a learning language, though Java and C# are better than C and C++. Python is easy to follow, and Forth is about as simple as programming gets, but Forth is harder to find good information on than Python. Perl is fun. Very fun. But unless you learn it the right way, you'll be confused (as you will with any language that can look like line noise without any effort).

My best suggestion is to get a list of programming …

>well dont know much about C++ standards
That's fine, but when I quote from either the C or C++ standard, it means I'm right. Just for future reference, because the standard is the ultimate authority on the matter, and no amount of linking to Schildt (not a good idea either way) or quoting K&R (which is never a bad idea) will change that.

>So i think in C the type of integral constants are very much defined.
C leaves open the possibility of extended integer types, but makes sure that in no way will an unsuffixed decimal constant resort to an unsigned type. The C standard gives a nice table where the allowed types for an unsuffixed decimal constant are int, long int, and long long int. The detail is thus:

If an integer constant cannot be represented by any types in its list, it may have an extended integer type, if the extended integer type can represent its value. If all of the types in the list for the constant are signed, the extended integer type shall be signed. If all of the types in the list for the constant are unsigned, the extended integer type shall be unsigned. If the list contains both signed and unsigned types, the extended integer type shall be signed or unsigned.

I've bolded the part that rules out a conversion to unsigned long, because the list for the relevant constant doesn't include unsigned types.

>the purpose of this program …

"The type of an unsuffixed integer constant is either int, long or unsigned long. The system chooses the first of these types that can represent the value."
--Taken from page no 118, chapter 3, "A book on C"(4th Edition) by AL KELLEY/IRA POHL.

Your book is wrong.

The type of an integer literal depends on its form, value, and suffix. If it is decimal and has no suffix, it has the first of these types in which its value can be represented: int, long int; if the value cannot be represented as a long int, the behavior is undefined. <snip octal and hexadecimal literals> If it is suffixed by u or U, its type is the first of these types in which its value can be represented: unsigned int, unsigned long int. If it is suffixed by ul, lu, uL, Lu, Ul, lU, UL, or LU, its type is unsigned long int.

A program is ill-formed if one of its translation units contains an integer literal that cannot be represented by any of the allowed types.

--Taken from Section 2.13.1 Integer Literals, paragraph 2, of the C++ standard.

>if the integer cannot be held in int then the compiler will automatically make
>it long and if the integer cannot be held as a long then it will make it Unsigned long
Close. Without a suffix, the type for an integer constant will start at int, then go to long int. If the value isn't representable by long int, the behavior is undefined. At the very least "in this context", a U (or u) suffix should be used to force the range to be unsigned int and then unsigned long int. By the way, if the literal doesn't fit in the allowed range, with or without a suffix, the program is broken.

>I don't know what is the difference of "void main()" and "int main()"?
void main() is wrong, int main() is correct. That's the only difference that's relevant.

Unless you want to do precise error handling and throw a message if the user enters something other than q or Q, you can simply place the entire processing code into an infinite loop and break if scanf fails:

#include <stdio.h> 
#include <stdlib.h>

/* Main Program */
int main(void)
{
  float USD;
  float CAD;
  float EUR;
  float GBP;
  float CHF;
  float YEN;
  int input;

  /*Title of program*/
  printf("\t This program will convert foreign currency to US Dollars\n\n");

  /*Assigning Values*/
  USD = 1.0f; /* US Dollar*/
  CAD = 1.2257f; /* Canadian Dollar*/
  EUR = 0.752162f; /* European Euro */
  GBP = .51573f; /* British Pound */
  CHF = 1.134f; /* Swiss Franc*/
  YEN = 1.038f; /* Japanese Yen*/

  for (;;) {
    printf("Please choose form the following list of currency or press q to quit.\n"); 
    printf("\n");
    printf("[1] Canadian Dollar\n");
    printf("[2] British Pound\n");
    printf("[3] European Euro\n");
    printf("[4] Swiss Franc\n");
    printf("[5] Japanese Yen\n"); 
    printf("\n");
    if (scanf("%d", &input) != 1)
      break;

    /*switching statements */
    switch (input)
    {
    case 1 : 
      printf("%1.6f Canadian Dollars is equal to %1.1f US Dollar.\n", CAD,USD);
      break;
    case 2 :
      printf("%1.6f European Euro is equal to %1.1f US Dollar.\n", EUR,USD); 
      break;
    case 3 :
      printf("%1.6f British Pound is equal to %1.1f US Dollar.\n", GBP,USD);
      break;
    case 4 : 
      printf("%1.6f Swiss Franc is equal to %1.1f US Dollar.\n", CHF,USD);
      break;
    case 5 :
      printf("%1.6f Japanese Yen is equal to %1.1f US Dollar.\n", YEN,USD); 
      break;
    }
  }

  return 0;
}

That's the easiest solution. If you want something more structured and good …

>but why this sample program doesn't work??!!
Integer literals are just that, integers. If you want a long literal, suffix it with L. If you want an unsigned long literal, suffix it with UL.

>void main(){
main returns an int, it always has and always will.

>Now i know why Narue refused to back down even if Narue's arguments
>were baseless, i was right Narue was a hater, a Java Hater - god help us all
You have yet to prove my arguments baseless. God forbid we actually get into a debate on the actual merits and flaws of Java. Though I can imagine how it would go. I would go down my list of well thought out and rational reasons for hating Java and you would end up saying "Nuh uh!", with a link to some irrelevant article advocating Java.

>Oh my god i didn't even knew such people existed this world.
That's because your head is so far up your own ass you can't smell the bullshit.

To recap: I don't like Java. I don't like C++. I do like C. I like and dislike quite a few languages that you've probably never heard of because you can only seem to speak Java, but that's beside the point. I know these languages and I use them all on a regular basis whether I like them or not. Why? Because they're tools. They help me to do my job, which is to solve problems. When I'm doing my job, I don't have time for petty purist thoughts like which language will be the next BIG thing and which languages are on their way out. I use what works, if I find something that works better I use that. Nothing you …

>it will take the ASCII value of a which is 97
We don't care whether you know what the integer values of the ASCII characters are. Stop assuming a specific character set. Geez, how many times do I have to repeat myself before you people get a clue?

please explain in detail how computer work.in term of computer processing cycle.for example when we start compuer how comper parts(ram,processor,hard disk,busses,etc )perform task or work.and how windows work.

This is a joke, right? Go do your own homework!

>Then what is the point to use pointer and new operator to declare the array in the first case?
Because the second case is ill-formed and thus, illegal in C++. Array sizes in C++ must be constant integral values. If it works when you try it then that's because your compiler allows it as an extension. Only the first case is guaranteed to be correct (assuming n is already defined).

>what has that got to do with anything expecially the popular part
Are you daft? Existing means that you can prove it's been done and popular means you can prove that the result is worth a damn. Since you can't seem to link me to anything conclusive, your arguments are falling on deaf ears.

>Which part of written in 100% pure Java you don't understand
It's impossible to write an operating system completely in Java. If you knew half of what you pretend to then you would realize this.

>He usually has a lot of interesting things to say on this topic
I've concluded that you're a troll, and you've been plonked. Have a nice life.

>if u can post the names of that kind of functions
Are you blind? I gave you the two functions that you need to do what you want to do, whether it's faking POSIX functions, or solving your problem with the straight Windows functions. Now go to MSDN and do the research on them. And in case you missed it the first two times:

FindFirstFile and FindNextFile

Geez.

>Now see the below thread
I won't accept that. Show me an existing and popular operating system written completely in Java except for parts that absolutely cannot be.

>Let me leave you with a quote
My eyes are just fine, you don't need to use bold and a huge font. I also don't care about your inappropriate quotes. Give me facts, not opinions, or I'll shrug you off as yet another moron who doesn't have a strong grasp of reality.

But you can't. All you can do is tell me what you think, or post links to threads that aren't nearly as deadset on the abolition of all languages not Java. Tell me, have you read those links in detail? One you used to prove that C++ is on the way out was merely talking about Java being here to stay. That's quite a difference, and it shows that the authors are better informed than you are.

Your inconclusive links that completely miss the point have changed my mind! I'm now a devout Java user who will never turn to other languages even if they appear better at first glance or are in a different problem domain than Java! All bow before Richard West for he is a genius!

Yours Sincerely

Someone with an open mind.

Asnwer me this. Java may be everyone's choice for writing new code. But what are we going to do with the hundreds of millions of lines of code that aren't Java? Are we going to convert it to Java just because it may be a better language? Because it may be simpler? Because it has an overwhelming set of "standard" libraries?

What about systems programming? Do you have a link that shows Java to be superior to C for writing an operating system efficiently? I don't see Sun writing Solaris in Java, do you?

Tell me, do you have a toolbox with nothing but a hammer because a hammer can "fix" any problem? I have nothing against Java, but I believe strongly that no language will solve all of your problems, simple things usually aren't, OOP is totally overrated and abused, and people who advocate any one language or methodology are closed minded fools.

Now, tell me where I'm wrong. Of course, I don't expect you to see the light simply because you're too entrenched in your own petty likes and dislikes to …