view release on metacpan or  search on metacpan

RELNOTES  view on Meta::CPAN

                  (this is a *mailing list* and you must be
                   a subscriber before posting)

    Home Page: http://www.arsperl.org

---------------------------------------------------------------------------

1.80 Notes
----------

The 1.80 release includes ARS 5.x integration. When compiling against
ARS 5.x APIs, the ars_NT* functions (notifier library) will no longer
work. The notifier system has completely changed in release 5.0 of
ARsystem.

Regardless of what version of API you compile against, the following 
functions have had their parameters altered which means that scripts 
will need to be editted (unless you are using the OO layer).

	Function			What's Changed
	--------------------------------------------------------------
	ars_GetListEntry		additional required  parameter
	ars_GetListEntryWithFields	additional required  parameter

The following functions have altered return values.

	Function			What's Changed
	--------------------------------------------------------------
	ars_GetCharMenu			for query menus, the 
					labelField is no longer
					a scalar. it's now an
					array ref.

	
1.68 Notes
----------

The 1.68 release includes ARS 4.5 integration. When compiling against ARS
4.5 APIs, the following data structures will change which _might_ break
existing scripts. You might need to update those scripts when recompiling
ARSperl against the 4.5 (or later) libraries.

	Data Structure			Used/Returned By
	--------------------------------------------------------------
	Active Link Hash		ars_GetActiveLink()
	Active Link Hash		ars_CreateActiveLink()
	Filter Hash			ars_GetFilter()
	Escalation Hash			ars_GetEscalation()

The majority of users should be unaffected by this since most probably
don't retrieve the actual definitions of these objects in their
scripts. 

In addition, ars_Import() has changed. It now has a different 
parameter list. This means that existing scripts will need to 
be updated. See the documentation on this function for details.


When compiling against an API revision prior to ARS4.5, the hashes returned 
by the above functions include a "schema" key which denotes which schema
the object is "attached" to. As of 4.5, it is possible to attach an object
to multiple schemas. The hash key has changed from a scalar (string) to an
array of (one or more) scalars and the name of the key has changed to
"schemaList". 

On an unrelated note, the ars_GetCharMenu() call now decodes the "menuType" 
hash key. Previously it was returned as a number (a raw enumeration value)
and you had to figure out on your own what that number meant. Now we decode 
it so you get a string telling you what sort of menu it is. This change was 
made to bring this function inline with how the other ARSperl functions
operate. Again, you might need to update some of your scripts. This change
is true regardless of what revision of the ARS API you compile against.

1.62 Notes
----------

The 1.62 release includes ARS 4.0 integration. There are a few things
that have changed regardless of what version of ARS you compile against 
and there are things that have changed only if you are compiling against
v4.0 (or greater).

First, regardless of what version of ARS you are compiling this against,
ars_perl_qualifier now takes a control struct (in addition to the  
encoded qualifier). When compiled against pre-4.0 APIs, the control struct
parameter is still required, but is ignored. IF YOU USE THIS ROUTINE IN 
EXISTING SCRIPTS, THEY WILL NEED TO BE CHANGED.

Previously, when perl executed "use ARS;" it would automatically trigger a
call to  ARS::__ars_init(). This routine was im`ortant for setting up
system specific stuff as well as preparing to connect to a private
server. Now this routine is part of ars_Login() because, as of 4.0, we need
the control structure that ars_Login() generates in order to call
ARInitialization (a.k.a. __ars_init). The __ars_init() routine is still
there and is callable, but doesn't do anything if you compile against ARS>=4.0

Similiarly, when your perl script exitted, ARS::__ars_Termination() was 
automatically called for you. This can no longer be done because we, once
again, need the control structure when we are cleaning up (to release licenses,
etc). So, the functionality of this routine is now rolled into ars_Logoff().
This means that if you don't call ars_Logoff when your script completes (or
when it prematurely exits) you might not release your license. This shouldn't
affect too many things, but is something to keep in mind. You might want to
place END{} clauses in your scripts that can call ars_Logoff() if/when your
script(s) die().

Also note that, as of v4.0, the ARS API is now multithreaded. This means that
you must linking the POSIX threads library when compiling ARSperl. I have
not determined what impact this has under Windows NT. I would guess none since NT
is normally a threaded environment - you probably get the appropriate thread
routines either way.

1.6 Notes
---------

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
---------