Quote:
Originally posted by kwigibo
I'd go with PHP too out of the lot but my second choice would be C/C++, then perl.
|
No offense meant, but how much CGI scripting have you done? With PHP? Perl? C? C++? how long have you been coding with each?
I've been coding in C for 10+ years, and perl for 2 years, I know php enough to get by... I love C, I always have... but I think I'd rather someone shot me in the foot than make me write a CGI in it.
Debugging a C CGI is not pretty. Development time in C is doubled (and sometimes more) over any scripting language such as perl or a browser based language, such as php or javascript.
Don't misunderstand me, C is always going to be my favorite, but every language has it's place. C and C++ can most certainly be used for CGI's and can in cases outperform scripts, but considering development time, I'd rather use perl. Now, if I had taken the time to develop an extensive library for handling alot of the memory management stuff and taking care of alot of the GC and such, I'd maybe reconsider... but why do that when php and perl make scripting a snap?
Of course, you may have some tools or experience I don't, which leads to your decision.. my personal opinion is simply that C and CGI don't mix well.
amartinez:
Does calling awk with a full path help, as startup suggested? If not, what does the error log say? It should provide you with details to determine what's going on..
My first thought was that awk was not printing to stdout.. I'm not sure what it defaults to, but you could probably force it to dump everything to stdout... just an idea.
TLD