ARSperl
view release on metacpan or search on metacpan
---------
The 1.6 release marks the first real NT port. v1.5x attempted a port
to Active State's Perl for Windows, but wasn't successful. Bill Middleton
re-worked the source code and merged it into Gurusamy Sarathy's
version of perl for windows.
1.5 Notes
---------
This release contains serveral bug fixes and minor feature additions.
An effort was made to implement the remaining ARS functions, however,
it proved to be very time consuming to implement and test them. Therefore,
in this release most of the remaining functions have been implemented.
The rest will likely be implemented in a future release. See TODO for
a list of remaining functions.
1.4 Notes
---------
The notifier functions have been added to the main package. This allows
Everything basically remains the same so you don't need to modify your
scripts. The only things that change are the NT (notification) routines
to a certain extent. However, since NT (notification) support is new to
this release, this shouldn't be a problem.
The doc has been reorganized as well.
1.3 Notes
---------
We've added some features for performance analysis. In particular,
we've added the "profiling" feature to ARSperl. Now, when you call
ars_Login() it initializes a profiling variable that will track
the number of queries your script makes against the server. You
can then access this information using the ars_GetProfileInfo() call.
We send this information to syslog() automatically at the end of
each script and then process the syslog file later on to keep stats
on our API scripts. In this fashion, we can quickly determine which
scripts are triggered the most, and which make the most queries. We
can then concentrate out optimization efforts on those particular
API scripts.
example/ars_QualDecode.pl view on Meta::CPAN
# a set of values (used for the "IN" operator)
# i've never really seen the "IN" keyword used
# either.. so i'll just flag it and dump something
# semi-appropriate.
elsif(defined($h->{valueSet})) {
$e = "valueSet(".join(',', @{$h->{valueSet}}).")";
}
# a local variable. this is in the API, but i dont think
# it's a real feature that is available.. perhaps
# something that remedy is working on? hmm..
elsif(defined($h->{variable})) {
$e = "variable($h->{variable})";
}
# an external query on another schema. not sure
# how this works so we'll let it go for now..
# i can't think of how this works for a filter
# or active link.. perhaps this is more "in development"
html/manual/OO/index.html view on Meta::CPAN
<BODY BGCOLOR="#FFFFFF">
<CENTER>
<H1>ARSperl Programmer's Manual - OO Layer Overview</H1>
</CENTER>
<H2> Objective </H2>
Since there are several (at least 3) separate OO layers out there, some of
which work on top of ARSperl and some of which don't, I decided to
implement a layer ontop of ARSperl so that you get all of the
features of ARSperl as well as an OO layer for a subset of those
features.
<H2> Features </H2>
The following features are available as part of the OO layer.
<DL>
<DT> <B> Exception Handlers </B> <DD>
The OO layer abstracts exception handling away a bit (optionally,
ofcourse). By default, the layer installs three handlers that are
called if an FATAL, ERROR, or WARNING return code is returned by
the ARS C API. At first, these handlers map to the Perl "die" and
"warn" functions. You can, however, disable or over-ride this
feature and install your own handlers. <P>
Have a look at the <A href="connection.html#new">Connection Object's
constructor method</A>. <P>
Also examine the <code>t/entry.t</code> script available in the
source distribution for an example of how to use this. <P>
Basically, what this means is you don't have to test the
return code of each call you make. If a call encounters a problem
while doing it's job, it'll call an exception handler to handle
( run in 0.398 second using v1.01-cache-2.11-cpan-a5abf4f5562 )