nall | An alternative standard library for C

You want to loop over question & answer pairs, until the question is blank:

Your deletePic function is broken in multiple places. Among them:

• Dereferencing an indeterminate pointer, yearNode
• Incorrect comparator (should use < ; not !=
• free'ing an indeterminate pointer.

The first and last of those are a recipe for disaster. If that function does what the menu claims it should, I think what you want is this:

You could use json module to parse content of script tags, which is accessible by .text field

Here is the example of parsing all script jsons and printing name:

It's looking up the worksheet1 attribute because you told it to:

Continuing from my comment, the primary problem you face is that you set the number of workers (i) at the beginning of your program and you use that value to size your niz VLA (Variable Length Array). Once set, it cannot be changed. So when you attempt to add additional workers later using you menu, you attempt to write beyond the end of your array (resulting in Undefined Behavior) causing the problem output you see.

Your alternatives are either to dynamically allocate storage for your workers and keep track of how many you have allocated and how many you have filled, and when filled == allocated you reallocate more storage. Another option is simply to declare some reasonable max number of workers you will have and then declare an array of that many, keeping track of the number added and when the number of workers added equals the array size -- just indicate the array is full. (though you can't expand the number of workers here)

An additional note about using VLAs. Beginning with the C11 standard, compiler support for VLAs was made optional -- though I don't know of any compilers that don't continue to support them.

Weaknesses In Your Code

The most glaring weakness is your failure to check the return of scanf() when a numeric conversion is required. That invites problems. Why? scanf() can fail in two ways (1) a matching-failure where the input provided doesn't match the conversion specified. (e.g. user enters "twenty-one" for age instead of 21). When a matching failure occurs, character extraction from the input buffer ceases at the point of failure -- leaving "twenty-one" unread in the input buffer -- just waiting to bite you on your next attempted input.

In fact if a matching-failure occurs before you enter you menu while(1) loop -- your code locks into an infinite loop.

(2) scanf() can fail with an input-failure where EOF is reached before the first valid conversion takes place. (a user can cancel input by generating a manual EOF with Ctrl + d, or `Ctrl + z on windows) If you don't check the return, you cannot handle either case.

Another weakness with your approach is using scanf() for user-input. Why? Because in the matching-failure case, or after any use, characters are left in stdin unread. In the normal case the '\n' is left unread, and if your next input isn't taken with scanf() and you don't extract the unread character(s), your next input will fail. This is one of the (many) pitfalls associated with using scanf(). Instead, as a general proposition, all user-input should be taken using fgets() and then any conversions should be handled by sscanf() from the buffer filled by fgets(). That way, with a sufficiently sized buffer, you are guaranteed to consume each line of input regardless of whether the subsequent conversion fails. No characters are left unread to impact the next input attempt.

Alternatives Approach

While the two different input functions may be a homework requirement, there is no need for different input functions to read one, and multiple workers. Just write a single function that can handle both. Since your input function can succeed or fail, you need to provide a meaningful return to the caller, so the success or failure of your input function can be validated at the point it was called. void return type is only sufficient for functions that have no bearing on the continued operation of your code (like print functions, etc..).

In your switch() statement, you should handle menu entries that are out-of-range. What if the user slips and enters 5 or -32 or "foo" for that matter? We addressed the matching-failure above, but to handle input that is out-of-range, simply providing a default: case can suffice. For example:

Its is very likely that phpmail function does not fit the anti-spam methords most providers use as the server the mail is being sent from is not recognised as allowed. DKIM, SPF, RIP need to be matched. To find out what gmail does not like about your email would be best to review the headers of the sent message to make sure it fits your domains sending criteria. However if you want to get this resolved quickly using an existing email account or creating a new one for your domain such as website@ and using STMP auth should prevent your emails getting flagged as the sending server should already match the needed criteria. Here is a link to a thread that should help: Sending email with PHP from an SMTP server

I can't run it but I think all problem is that it gets information about 500 photos - because you have per_page=500 - and it runs for-loop for all 500 photos and you have to wait for the end of for-loop.

You should use break to exit this loop after n images

Name the list of dataframes. A simple way to do that would be to use tibble::lst

You are using a + at the end of the second line where there should be a dplyr pipe %>%. That produces the given error.