Well, firstly, it ain't CGI, it's network programming. Well, it's slightly one sublayer below HTML, it's HTTP request/response headers. Thus, print, <>, read, write are not advisable, thus resorting to these.
However, I would like to thank both felix and drieux for addressing this problem. Seems like i have to tackle the problem from another perspective then. Thanks! Advice still welcome! ----- Original Message ----- From: "drieux" <[EMAIL PROTECTED]> To: "cgi cgi-list" <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 10:06 PM Subject: Re: Sysread and syswrite > > On Wednesday, May 22, 2002, at 01:07 , ChaoZ InferNo wrote: > [..] > > I want to print out a variable to my client over the internet, but would > > like to use syswrite and sysread would help to reduce mistakes in EOF > > characters. > [..] > > I back felix's main line - since sysread/syswrite are for > accessing files - not variables already in your code. > > So why are you concerned about 'EOF' characters???? > What is leading your analysis there??? > > may I recommend > http://www.wetware.com/drieux/pbl/cgi/basicPagePopper.txt > > as a simple basic 'how to get the Page Out the Door' with > > use CGI; > > since it shows the simple > > start_html(...) > # do some stuff > end_html; > > remember as many author's of new things have learned after > reading the book on it - 'wow, even I didn't know that...' > so everyone is new to stuff, till they have experienced it all. > > ciao > drieux > > --- > > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
