The simplest naive solution is simply: $file = “/path/to/file”; $data = file($file); $line = $data[count($data)-1]; Though, this WILL load the whole file into memory. Possibly a problem (or not). A better solution is this: $file = escapeshellarg($file); // for the security concious (should be everyone!) $line = `tail -n 1 $file`;
here a concatenation solution: #include <stdio.h> #include <stdlib.h> #include <string.h> #define BUFFERSIZE 10 int main() { char *text = calloc(1,1), buffer[BUFFERSIZE]; printf(“Enter a message: \n”); while( fgets(buffer, BUFFERSIZE , stdin) ) /* break with ^D or ^Z */ { text = realloc( text, strlen(text)+1+strlen(buffer) ); if( !text ) … /* error handling */ strcat( text, … Read more
The behavior is different in newer releases of glibc, for n == 1, it returns s which indicates success, this is not an unreasonable reading of 7.19.7.2 The fgets function paragraph 2 which says (it is the same in both C99 and C11, emphasis mine): char *fgets(char * restrict s, int n, FILE * restrict … Read more
The function fgets might add a newline at the end of the string read. You’ll have to check that: size_t ln = strlen(input) – 1; if (input[ln] == ‘\n’) input[ln] = ‘\0’; or even strtok(input, “\n”);
In order to use gets safely, you have to know exactly how many characters you will be reading, so that you can make your buffer large enough. You will only know that if you know exactly what data you will be reading. Instead of using gets, you want to use fgets, which has the signature … Read more
I’ll bet it’s because of the \n stuck in the input stream. See one of these questions: I am not able to flush stdin. How do I go about Flushing STDIN here? scanf() causing infinite loop or this answer. Also: Why not to use scanf(). P.S. fgets() is a function, not an instruction.
If you don’t need any special processing, this should do what you’re looking for $lines = file($filename, FILE_IGNORE_NEW_LINES);
Never use gets. It offers no protections against a buffer overflow vulnerability (that is, you cannot tell it how big the buffer you pass to it is, so it cannot prevent a user from entering a line larger than the buffer and clobbering memory). Avoid using scanf. If not used carefully, it can have the … Read more
strcmp is one of the few functions that has the reverse results of true and false…if the strings are equal, the result is 0, not 1 as you would think…. if (strcmp(a, b)) { /* Do something here as the strings are not equal */ } else { /* Strings are equal */ } Speaking … Read more
scanf() reads exactly what you asked it to, leaving the following \n from the end of that line in the buffer where fgets() will read it. Either do something to consume the newline, or (my preferred solution) fgets() and then sscanf() from that string.