On Monday, Jun 9, 2003, at 13:05 US/Pacific, steve ryan wrote: [..]
So... i do my hex to ascii translation first, and the character replace second.
so simple.
AARRRGH! :)
Huzzah!
Welcome on the BigBus!!! Those who have headBashed in public that
DuhMoment....
There is always this ungainly problem of what the documentation says about how things should happen, and then understanding where exactly they really DO happen... As we have been sharing with David Greenhalgh, a part of the issue is understanding IF the problem is with the perl syntax, or with how a given browser/server is doing it's bit.... and then there is the 3Dom's Problem....
I should also thank you steve, as I finally took the time to clean up a bit of ugliness when I saw it in the function when I went to show it to you.... One of those things I have been meaning to go back and better understand and refactor... so my complements for getting me off the dime...
On Monday, Jun 9, 2003, at 09:48 US/Pacific, Kristofer Hoch wrote:
[ lovely code snippet for reasons of National Security ]Also, Maybe you may want to try using CGI.pm to get query strings.
====================== That may help you out quite a bit. Drieux, You are so hard core dude!;)
I was rather counting on you to defend the 'mainstream' position - and why/how it would work in canonical CGI.pm....
On top of the usual problems about producing useable html stuff that will work with IE and Netscape, and opera, and... there is the 'server side' problems about what assumptions does one have about what will 'be there' when your code arrives; and some here can go back and notice, as I did, that the CGI.pm is a relatively 'new' addition - as I have one of the boxes that has the fan out of perl 5.003(??) - may 6th 1997 - that did not deliver a CGI.pm.... Some of the folks who ask questions here are also running off of servers that come from those dark times, a long, long, long time ago...
A part of the problem of course is whether or not one has control of any form over what the sys-admin on a given site will actually be doing with how much of perl is actually installed.
So one either has to call out the full on dependency list,
perl 5.6.1 or better
and ..... and ....And PRAY that the nice sys-admin/WebPerKin will be ever so polite as to make sure that the new cool and groovey modules that one really likes are in place....
Or one opts for alternative strategies such as hacking code that lives in the middle ground which does not assume more than one can hope for....
When that project started, there was some uncertainty how far back we were going to have to be 'compatible' - so some things have to be hacked around.... So by the time it was 'ok' to presume that we would not have to go back before 5.6.1, most of the cgi basics had been tweeked, and there really was no good reason to try to fall back to CGI.pm ...
The Other Side of the argument of course is the value I personally place on,
Rip It Apart,
Put It back together....So It is my OCD to see how much I really 'know' about the stuff I am coding up, and why I like this Kult Solution over that...
A part of what we need to be able to share with all FNG's is that basic reality,
We all start some place...
and hopefully also share with them our
'Once Upon a Time, I did a dumb thing like,
and so I tend to do....'things that we all do...
Fortunately I caught the 'oh that looks ugly' in the function, as noted above, BEFORE I sent it to the list.... at least this time.
ciao drieux
---
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
