2

The problem is simple. You have created two string arrays. Each holds the 26 letter alphabet, one lower case, the other upper case. They are created in sequential memory. In this case, the UC array is first, followed immediately by the lc array. You then try to print them out as strings, using the base variable (i.e., uppercase and lowcase) as the ...


2

From the documentation: "The C library function time_t time(time_t *seconds) returns the time since the Epoch (00:00:00 UTC, January 1, 1970), measured in seconds. If seconds is not NULL, the return value is also stored in variable seconds." If the parameter is NULL instead of a var, the function just returns the number of seconds. This is a common ...


1

The only thing wrong in your searching algorithm that i'm seeing is that you have your if statement followed by a second if statement. I believe that that should be an else if.


1

The man page for srand48 includes the lines: Feature Test Macro Requirements for glibc (see feature_test_macros(7)): All functions shown above: _SVID_SOURCE || _XOPEN_SOURCE You'll find everything you need to know about Feature Test Macros at man 7 feature_test_macros Pay special attention to: NOTE: In order to be effective, a feature test macro must be ...


1

I don't think anyone has figured that one out. It may not be possible, but I would be happy for someone to prove me wrong. OTOH, why do you want to work with so much input data in the debugger? Wouldn't you be better off manually entering data as you step through the program, and restricting the data input to only 3 or 4 elements in the list? Inputting 50 ...


Only top voted, non community-wiki answers of a minimum length are eligible