Click here to Skip to main content
16,021,430 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
#include <stdio.h>
#include <stdlib.h>


float vsota(int a, int m, float sum); 
 {
  for(m=1; m<a; m++)
  {
   sum +=1./(m*(2.*m+1.)); 
  }
  return sum; 
 }
void main ()
{
 int m, a; 
 float sum; 
 printf("Stevilo clenov:"); 
 scanf("%d", &a); 
	
 printf("Vsota clenov je: %f", vsota((int)a, (int)m, (float)sum)); 
}


What I have tried:

that is in c++. pleas i need help
Posted
Updated 22-Dec-22 8:05am

Your program looks more C than C++, actually.
It seems you are trying to compute the sum of the terms
1/(n * ( 2 * n + 1))
with n = 1, 2, .., (a-1)

Then the vsota function should take just one parameter, namely a:
C
double vsota(int a)</code>

(note I used double, it is a better choice than float almost anywhere)
Then you need to accordingly change the function call, inside main, where you should also discard the useless m and sum variables.
Being nitpick, I also suggest you to use the compliant main definition:
C
int main()
{
  //...
}

To summarize (incorporating also Griff's fix):
C
#include <stdio.h>
#include <stdlib.h>


double vsota(int a)
{
  double sum = 0.0;

  for (int m = 1; m < a; ++m)
  {
    sum += 1.0 / (m * ( 2.0 * m  + 1.0 ));
  }
  return sum;
}

int main()
{
  int a;
  printf("Stevilo clenov: ");
  scanf("%d", &a);

  printf("Vsota clenov je: %f\n", vsota(a));
}
 
Share this answer
 
v2
Semicolons ... they matter.
This one should not be there:
C
float vsota(int a, int m, float sum); 
                                    ^
                                    |
 {
  for(m=1; m<a; m++)
  {
You should expect to get syntax errors every day, probably many times a day while you are coding - we all do regardless of how much experience we have! Sometimes, we misspell a variable, or a keyword; sometimes we forget to close a string or a code block. Sometimes the cat walks over your keyboard and types something really weird. Sometimes we just forget how many parameters a method call needs.

We all make mistakes.

And because we all do it, we all have to fix syntax errors - and it's a lot quicker to learn how and fix them yourself than to wait for someone else to fix them for you! So invest a little time in learning how to read error messages, and how to interpret your code as written in the light of what the compiler is telling you is wrong - it really is trying to be helpful!

So read this: How to Write Code to Solve a Problem, A Beginner's Guide Part 2: Syntax Errors[^] - it should help you next time you get a compilation error!

And spending a little time learning to understand syntax error messages will save you a huge amount of time in future: you waited at least 1/4 hour for Chris to reply, then your email system probably added another 10 minutes or so, plus the time it took you to type up the question once you had found this site and created an account. Chances are that you could have saved a significant chunk of that time if you knew how to read them!

I'm not saying we don't want to help you fix them - sometimes I can't see my own errors because I read what I meant to write - but fixing syntax errors is part of the job, and if you can't do it for yourself people are going to look at you as a bit weird should you get a job in the industry!
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900