0
I am trying to practice more problems on hackerrank the problem is i am facing a no response of stdout error more frequently.
Can someone give me a good advice on how to avoid it?
12 Réponses
+ 1
you sent me pastebin code with no output to file
look to my code at line 56
fout<<ways; // this line must be added
+ 1
Tq buddy it's working fine now zemiak
0
show code
(but I don't solve c++ now)
0
https://code.sololearn.com/cyTR5xaHqjCs/?ref=app
I had done this code this had produced correct output for coin change problem in sololearn and in my eclipse but when pasting this code in hackerrank ide it produces no response of stdout.I had even tried with other programs but it produces the same no response of stdout error.I am attaching the problem link below
https://www.hackerrank.com/challenges/coin-change/problem
0
Had even tried with other codes in leaderboard but it produces the same no response on stdout error
0
I am trying to avoid this error but I am not finding the cause
0
The challenge was from dynamic programming and not from c++ cateogory of c++
0
you must write an answer to the fout file instead of cout
study the original default code (you can reset the solution if you have a copy of your solution somewhere), there's a fout line.
I was success with it.
ofstream fout(getenv("OUTPUT_PATH"));
...
long ways = getWays(n, c);
fout<<ways;
...
0
Ya I had changed my code to that format also and tried to get output in many types of codes in leaderboard but still that error persisted.Will send the code in that format
0
this is my complete code with your solution, what is your, what is different ?
https://pastebin.com/enZy2PwV
I try run only, not submit, (c++ / c++14) but I get this:
"Congratulations!
You have passed the sample test cases. Click the submit button to run your code against all the test cases."
0
zemiak my program looks similar and it looks like this
https://pastebin.com/jx3453bs
0
zemiak and I tried it with other programs but it produces the similar output of "no response on stdout".I still can't be able to find the cause of this error