Aaron,
Please feel free to implement the inline::sql
it was just an example!
Yes it would be a usefull tool,
especially because you can then separate your sql
cleanly.
The example I gave is just to demonstrate the idea of
getting a complex feedback from the backend system.
I am working on a project called gcc introspector,
where I patch the gcc compiler to dump out all of its
nodes.
Currently I invoke perl from inside the complier via
popen and stream out XML to it, which is translated
and put into a DBI/Postgres database.
I would like to be able to use the introspector from
inline:
so I can take a chunk of c-code,
inline::gcc::introspector it and then be able to
process the parse tree in perl!
>From the outside, I guess it possible to have a one
way communication, where I read in all the output of
the compiler. It could stream everything to stdout and
I could parse it from inside of inline using xml
parser....
what do you think?
mike
--- Aaron J Mackey <[EMAIL PROTECTED]> wrote:
>
> A bit offtopic from the OP's question, but your
> Inline::SQL looks very
> cute; is there actually a package out there like
> this (forget
> DBIx::Catalog and similar)? My DBI scripts usually
> looks like this:
>
> my %sths = ( 'get_user_from_name', q{SELECT user_id
> from users where name = ?},
> ..., ...
> );
>
> while(my ($key, $sth) = each %sths) {
> $sths{$sth} = $dbh->prepare($sth);
> }
>
> # ... use $sth{get_user_from_name}->execute($name),
> etc;
>
> So your Inline::SQL would allow me to put all those
> nasty SQL statements
> at the bottom of my scripts (or in another file
> altogether), and let me
> forget about them!
>
> -Aaron
>
=====
James Michael DuPont
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
