if you want to "list the functions in a library", you should look at the header file(s) aka .h file(s).
if you wanna search for functions in the standard library, you could execute
man -f keyword
to search for man pages referenced by keyword or
man -k keyword
to search man page descriptions and names for keyword as a regular expression.
You can find the current cs50.c and cs50.h files in /usr/src/libcs50 in the IDE. Suggest running update50 to make sure that you have the most current versions as it does get updated from time to time.
If this answers your question, please click on the check mark to accept. Let's keep up on forum maintenance. ;-)
string name = get_string ("What is your name?\n");
This line needs to be inside the main function.
It also needs to be before printf("hello, %s\n", name); this line, since you can't use the name variable until after it exists.
You don't need to update the cs50 library, your problem is that your make command is using the default implicit rules to determine what to do when there is no makefile, then when the action is determined it uses the content of make's predefined variables to execute a determined command. And this default command is not linking the cs50 library.
I think in ...
It is difficult to respond in a simple way, without going into great depths we can find very good documentation in man pages: We can find documentation of the standard head files by typing in the terminal
for example. With non-standard files like cs50.h this does not work, but we can find all the header files in the path
Just for reference, the problem was that the OP installed Oracle's JDK manually, and the directories containing the JDK's programs were not on root's PATH. That's why sudo make install failed, when it was trying to use jar.
There's more than one solution to this problem, including putting these directories on root's PATH, or softlinking the program's to ...
I may be wrong, but it seems to me that if you zip all the files together in the directory that you built the executable, including the modified make file, and then upload, it should work. If not, you can always resubmit a working solution later.
As a test, look at the command used to run check50 locally:
check50 2014.fall.pset5.speller dictionary.c ...