I'm wondering, I've created a file Connect.pm that interlinks LinkSQL with WWWThreads.
This is all it is:
use w3ttheme qw(%theme);
use w3tvars qw(%config);
use vars qw($dbh $VERSION %lang);
use lib '..';
use Links;
use Links::DB_Utils;
use Links::DBSQL;But the thing is there are some routines I'm worried will get confused. The only subs I could find by the same name were in w3t.pm and DBSQL.pm. &authentic I already took care of as this was one of the main reasons for doing this...for the most part I'm not worried about the w3t programs getting the wrong one because he mostly calls his functions w3t::function_name(...);
But in DBSQL.pm there is &do () , &prepare() that I'm somewhat worried about as they are also SQL functions, so if in a w3t sub the do function is called will it use the SQL call or will it use the DBSQL version?
I'm worried about any kind of conflicts arising between the w3t.pm and DBSQL subs or restrictions, but what doesn't make sense is that this particular one is a SQL function.
Can you (or someone) give me their thoughts on how this might create errors and affect perfomance, pretty please
.
This is all it is:
Code:
use strict; use w3ttheme qw(%theme);
use w3tvars qw(%config);
use vars qw($dbh $VERSION %lang);
use lib '..';
use Links;
use Links::DB_Utils;
use Links::DBSQL;
But in DBSQL.pm there is &do () , &prepare() that I'm somewhat worried about as they are also SQL functions, so if in a w3t sub the do function is called will it use the SQL call or will it use the DBSQL version?
I'm worried about any kind of conflicts arising between the w3t.pm and DBSQL subs or restrictions, but what doesn't make sense is that this particular one is a SQL function.
Can you (or someone) give me their thoughts on how this might create errors and affect perfomance, pretty please
. 
Alex I think this one's for you...