The thing is that that wrapper is being used by many different programmers. The data containing the # is not under my control, so i can't backslash it before i get it. The problem is that in certain scripts (I don't know how many, cause here there's thousands...) the # is being interpreted as a comment, when printing, probably. but i can't change the final scripts, since i don't know how many are all of them, and politically i'm not allowed. So the best point seems to change the wrapper wich is the common node to all of them.
Ignacio Trabado Castillo
Dpto. Informática Desarrollo
tlf: 93 500 (9255)
| [EMAIL PROTECTED] (Chris Wagner)
Enviado por: [EMAIL PROTECTED] 21/06/2005 10:44
|
Para: perl-win32-users@listserv.ActiveState.com cc: Asunto: Re: filtering the output of fetchrow |
At 09:31 AM 6/21/05 +0200, [EMAIL PROTECTED] wrote:
>For the moment, it works right but there's a problem, COBOL fools have
>inserted in the database registers with '#' so i have to filter it, in
>order to avoid programs processing the char. Anyone can please give me an
>idea of the best way to modify my wrapper function fetchrow_sql to filter
>the results before passing them onto the external code?
What kind of problem is the # causing? Having a # sign in a variable
shouldn't cause any problem, perl is pretty good about that. If you need to
type a # in a place where it's being interpreted as a comment, just put a
backslach in front of it. \# You can also put in the backslash to escape
the # for use by some external function/program. $var =~ s/\#/\\\#/g
--
REMEMBER THE WORLD TRADE CENTER ---=< WTC 911 >=--
"...ne cede males"
00000100
_______________________________________________
Perl-Win32-Users mailing list
Perl-Win32-Users@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
