<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>P4 - OO interface to the Perforce SCM System.</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:root@localhost" />
</head>
<body style="background-color: white">
<p><a name="__index__"></a></p>
<!-- INDEX BEGIN -->
<ul>
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<li><a href="#base_methods">BASE METHODS</a></li>
<li><a href="#shortcut_methods">SHORTCUT METHODS</a></li>
<li><a href="#compatibility_with_previous_versions">COMPATIBILITY WITH PREVIOUS VERSIONS</a></li>
<li><a href="#licence">LICENCE</a></li>
<li><a href="#author">AUTHOR</a></li>
<li><a href="#see_also">SEE ALSO</a></li>
</ul>
<!-- INDEX END -->
<hr />
<p>
</p>
<h1><a name="name">NAME</a></h1>
<p>P4 - OO interface to the Perforce SCM System.</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
<pre>
use P4;
my $p4 = new P4;</pre>
<pre>
$p4->SetClient( $clientname );
$p4->SetPort ( $p4port );
$p4->SetPassword( $p4password );
$p4->Connect() or die( "Failed to connect to Perforce Server" );
my $info = $p4->Run( "info" );
$p4->Edit( "file.txt" ) or die( "Failed to edit file.txt" );
$p4->Disconnect();</pre>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
<p>This module provides an OO interface to the Perforce SCM system that
is designed to be intuitive to Perl users. Data is returned in Perl
arrays and hashes and input can also be supplied in these formats.</p>
<p>Each P4 object represents a connection to the Perforce Server, and
multiple commands may be executed (serially) over a single connection.</p>
<p>
</p>
<hr />
<h1><a name="base_methods">BASE METHODS</a></h1>
<dl>
<dt><strong><a name="item_new">P4::new()</a></strong>
<dd>
<p>Construct a new P4 object. e.g.</p>
</dd>
<dd>
<pre>
my $p4 = new P4;</pre>
</dd>
</li>
<dt><strong><a name="item_identify">P4::Identify()</a></strong>
<dd>
<p>Print build information including P4Perl version and Perforce API
version.</p>
</dd>
<dd>
<pre>
print P4::Identify();</pre>
</dd>
</li>
<dt><strong><a name="item_connect">P4::Connect()</a></strong>
<dd>
<p>Initializes the Perforce client and connects to the server.
Returns false on failure and true on success.</p>
</dd>
</li>
<dt><strong><a name="item_debuglevel">P4::DebugLevel( [ level ] )</a></strong>
<dd>
<p>Gets and optionally sets the debug level. Without an argument, it
just returns the current debug level. With an argument, it first updates
the debug level and then returns the new value.</p>
</dd>
<dd>
<p>For example:</p>
</dd>
<dd>
<pre>
$client->DebugLevel( 1 );
$client->DebugLevel( 0 );
print( "Debug level = ", $client->DebugLevel(), "\n" );</pre>
</dd>
</li>
<dt><strong><a name="item_dropped">P4::Dropped()</a></strong>
<dd>
<p>Returns true if the TCP/IP connection between client and server has
been dropped.</p>
</dd>
</li>
<dt><strong><a name="item_errorcount">P4::ErrorCount()</a></strong>
<dd>
<p>Returns the number of errors encountered during execution of the last
command</p>
</dd>
</li>
<dt><strong><a name="item_errors">P4::Errors()</a></strong>
<dd>
<p>Returns a list of the error messages received during execution of
the last command.</p>
</dd>
</li>
<dt><strong><a name="item_formatspec">P4::FormatSpec( type, string )</a></strong>
<dd>
<p>Converts a Perforce form of the specified type (client/label etc.)
held in the supplied hash into its string representation. Note that
shortcut methods are available that obviate the need to supply the
type argument. The following two examples are equivalent:</p>
</dd>
<dd>
<pre>
my $client = $p4->FormatSpec( "client", $hash );
my $client = $p4->FormatClient( $hash );</pre>
</dd>
<dd>
<p>See the section on SHORTCUT METHODS below for more information
on the abbreviated forms.</p>
</dd>
</li>
<dt><strong><a name="item_disconnect">P4::Disconnect()</a></strong>
<dd>
<p>Terminate the connection and clean up. Should be called before exiting.</p>
</dd>
</li>
<dt><strong><a name="item_getcharset">P4::GetCharset()</a></strong>
<dd>
<p>Return the name of the current charset in use. Applicable only when
used with Perforce servers running in unicode mode.</p>
</dd>
</li>
<dt><strong><a name="item_getclient">P4::GetClient()</a></strong>
<dd>
<p>Returns the current Perforce client name. This may have previously
been set by SetClient(), or may be taken from the environment or
P4CONFIG file if any. If all that fails, it will be your hostname.</p>
</dd>
</li>
<dt><strong><a name="item_getcwd">P4::GetCwd()</a></strong>
<dd>
<p>Returns the current working directory as your Perforce client sees
it.</p>
</dd>
</li>
<dt><strong><a name="item_gethost">P4::GetHost()</a></strong>
<dd>
<p>Returns the client hostname. Defaults to your hostname, but can
be overridden with <a href="#item_sethost"><code>SetHost()</code></a></p>
</dd>
</li>
<dt><strong><a name="item_getpassword">P4::GetPassword()</a></strong>
<dd>
<p>Returns your Perforce password. Taken from a previous call to
<a href="#item_setpassword"><code>SetPassword()</code></a> or extracted from the environment ( $ENV{P4PASSWD} ),
or a P4CONFIG file.</p>
</dd>
</li>
<dt><strong><a name="item_getport">P4::GetPort()</a></strong>
<dd>
<p>Returns the current address for your Perforce server. Taken from
a previous call to SetPort(), or from $ENV{P4PORT} or a P4CONFIG
file.</p>
</dd>
</li>
<dt><strong><a name="item_isparseforms">P4::IsParseForms()</a></strong>
<dd>
<p>Returns true if ParseForms mode is enabled on this client.</p>
</dd>
</li>
<dt><strong><a name="item_istagged">P4::IsTagged()</a></strong>
<dd>
<p>Returns true if Tagged mode is enabled on this client.</p>
</dd>
</li>
<dt><strong><a name="item_mergeerrors">P4::MergeErrors( [0|1] )</a></strong>
<dd>
<p>For backwards compatibility. In previous versions of P4Perl, errors
and warnings were mixed in the same 'Errors' array. This made it
tricky for users to ignore warnings, but still look out for errors.
This release of P4Perl stores them in two separate arrays. You can get
the list of errors, but calling P4::Errors(), and the list of warnings
by calling P4::Warnings(). If you want to revert to the old behaviour,
you can call this method to revert to the old behaviour and all
warnings will go into the error array. i.e.</p>
</dd>
<dd>
<pre>
$p4->MergeErrors( 1 );
$p4->Sync();
$p4->MergeErrors( 0 );</pre>
</dd>
</li>
<dt><strong><a name="item_parseforms">P4::ParseForms()</a></strong>
<dd>
<p>Request that forms returned by commands such as <code>$p4->GetChange()</code>, or
<code>$p4->Client( "-o" )</code> be parsed and returned as a hash reference for easy
manipulation. Must be called prior to calling <a href="#item_connect"><code>Connect()</code></a>.</p>
</dd>
</li>
<dt><strong><a name="item_parsespec">P4::ParseSpec( type, string )</a></strong>
<dd>
<p>Converts a Perforce form of the specified type (client/label etc.)
held in the supplied string into a hash and returns a reference to
that hash. Note that shortcut methods are available to avoid the
need to supply the type argument. The following two examples are
equivalent:</p>
</dd>
<dd>
<pre>
my $hash = $p4->ParseSpec( "client", $clientspec );
my $hash = $p4->ParseClient( $clientspec );</pre>
</dd>
<dd>
<p>See the section on SHORTCUT METHODS below for more information
on the abbreviated forms.</p>
</dd>
</li>
<dt><strong><a name="item_password">P4::Password( $oldpass, $newpass )</a></strong>
<dd>
<p>Run a <code>p4 password</code> command to change the user's password from
$oldpass to $newpass. Not to be confused with P4::SetPassword.</p>
</dd>
</li>
<dt><strong><a name="item_run">P4::Run( cmd, [$arg...] )</a></strong>
<dd>
<p>Run a Perforce command returning the results. Since Perforce commands
can partially succeed and partially fail, you should check for errors
using <a href="#item_errorcount"><code>P4::ErrorCount()</code></a>.</p>
</dd>
<dd>
<p>Results are returned as follows:</p>
</dd>
<dd>
<pre>
An array of results in array context.
undef in scalar context if result set is empty.
A scalar result in scalar context if only one result exists.
An array ref in scalar context if more than one result exists.</pre>
</dd>
<dd>
<p>This means you can get the result format you want by correct
use of Perl context. For example, if you always want an array,
use array context:</p>
</dd>
<dd>
<pre>
@results = $p4->Run( "sync" );</pre>
</dd>
<dd>
<p>Through the magic of the AutoLoader, you can also treat the
Perforce commands as methods, so:</p>
</dd>
<dd>
<pre>
$p4->Edit( "filename.txt );</pre>
</dd>
<dd>
<p>is equivalent to</p>
</dd>
<dd>
<pre>
$p4->Run( "edit", "filename.txt" );</pre>
</dd>
<dd>
<p>Note that the format of the scalar or array results you get
depends on (a) whether you're using tagged (or form parsing) mode
(b) the command you've executed (c) the arguments you supplied and
(d) your Perforce server version.</p>
</dd>
<dd>
<p>In tagged or form parsing mode, ideally each result element will be
a hashref, but this is dependent on the command you ran and your server
version.</p>
</dd>
<dd>
<p>In non-tagged mode (the default), each result element will be a string.
In this case, also note that as the Perforce server sometimes asks the
client to write a blank line between result elements, some of these result
elements can be empty.</p>
</dd>
<dd>
<p>Mostly you will want to use form parsing (and hence tagged) mode. See
ParseForms().</p>
</dd>
<dd>
<p>Note that the return values of individual Perforce commands are not
documented because they may vary between server releases.</p>
</dd>
<dd>
<p>If you want to be correlate the results returned by the P4 interface with
those sent to the command line client try running your command with RPC
tracing enabled. For example:</p>
</dd>
<dd>
<pre>
Tagged mode: p4 -Ztag -vrpc=1 describe -s 4321
Non-Tagged mode: p4 -vrpc=1 describe -s 4321</pre>
</dd>
<dd>
<p>Pay attention to the calls to client-FstatInfo(), client-OutputText(),
client-OutputData() and client-HandleError(). <em>Each call to one of these
functions results in either a result element, or an error element.</em></p>
</dd>
</li>
<dt><strong><a name="item_serverlevel">P4::ServerLevel()</a></strong>
<dd>
<p>Returns an integer specifying the server protocol level. This is not the
same as, but is closely aligned to, the server version. To find out your
server's protocol level run 'p4 -vrpc=5 info' and look for the server2
protocol variable in the output.</p>
</dd>
<dd>
<p>Must be called after running a command.</p>
</dd>
</li>
<dt><strong><a name="item_setapilevel">P4::SetApiLevel( integer )</a></strong>
<dd>
<p>Specify the API compatibility level to use for this script.
This is useful when you want your script to continue to work on
newer server versions, even if the new server adds tagged output
to previously unsupported commands.</p>
</dd>
<dd>
<p>The additional tagged output support can change the server's
output, and confound your scripts. Setting the API level to a
specific value allows you to lock the output to an older
format, thus increasing the compatibility of your script.</p>
</dd>
<dd>
<p>Must be called before calling P4::Connect(). e.g.</p>
</dd>
<dd>
<pre>
$p4->SetApiLevel( 57 ); # Lock to 2005.1 format
$p4->Connect() or die( "Failed to connect to Perforce" );
etc.</pre>
</dd>
</li>
<dt><strong><a name="item_setcharset">P4::SetCharset( $charset )</a></strong>
<dd>
<p>Specify the character set to use for local files when used with a
Perforce server running in unicode mode. Do not use UNLESS your
Perforce server is in unicode mode. Must be called before calling
P4::Connect(). e.g.</p>
</dd>
<dd>
<pre>
$p4->SetCharset( "winansi" );
$p4->SetCharset( "iso8859-1" );
$p4->SetCharset( "utf8" );
etc.</pre>
</dd>
</li>
<dt><strong><a name="item_setclient">P4::SetClient( $client )</a></strong>
<dd>
<p>Sets the name of your Perforce client. If you don't call this
method, then the clientname will default according to the normal
Perforce conventions. i.e.</p>
</dd>
<dd>
<pre>
1. Value from file specified by P4CONFIG
2. Value from $ENV{P4CLIENT}
3. Hostname</pre>
</dd>
</li>
<dt><strong><a name="item_setcwd">P4::SetCwd( $path )</a></strong>
<dd>
<p>Sets the current working directory for the client. This should
be called after the <a href="#item_connect"><code>Connect()</code></a> and before the Run().</p>
</dd>
</li>
<dt><strong><a name="item_sethost">P4::SetHost( $hostname )</a></strong>
<dd>
<p>Sets the name of the client host - overriding the actual hostname.
This is equivalent to 'p4 -H <hostname>', and really only useful when
you want to run commands as if you were on another machine. If you
don't know when or why you might want to do that, then don't do it.</p>
</dd>
</li>
<dt><strong><a name="item_setinput">P4::SetInput( arg )</a></strong>
<dd>
<p>Save the supplied argument as input to be supplied to a subsequent
command. The input may be: a hashref, a scalar string or an array
of hashrefs or scalar strings. Note that if you pass an array the
array will be shifted once each time the Perforce command being
executed asks for user input.</p>
</dd>
</li>
<dt><strong><a name="item_setmaxresults">P4::SetMaxResults( value )</a></strong>
<dd>
<p>Limit the number of results for subsequent commands to the value
specified. Perforce will abort the command if continuing would
produce more than this number of results. Note that once set,
this limit remains in force. You can remove the restriction by
setting it to a value of 0.</p>
</dd>
</li>
<dt><strong><a name="item_setmaxscanrows">P4::SetMaxScanRows( value )</a></strong>
<dd>
<p>Limit the number of records Perforce will scan when processing
subsequent commands to the value specified. Perforce will abort
the command once this number of records has been scanned. Note
that once set, this limit remains in force. You can remove the
restriction by setting it to a value of 0.</p>
</dd>
</li>
<dt><strong><a name="item_setpassword">P4::SetPassword( $password )</a></strong>
<dd>
<p>Specify the password to use when authenticating this user against
the Perforce Server - overrides all defaults. Not to be
confused with P4::Password().</p>
</dd>
</li>
<dt><strong><a name="item_setport">P4::SetPort( [$host:]$port )</a></strong>
<dd>
<p>Set the port on which your Perforce server is listening. Defaults
to:</p>
</dd>
<dd>
<pre>
1. Value from file specified by P4CONFIG
2. Value from $ENV{P4PORT}
3. perforce:1666</pre>
</dd>
</li>
<dt><strong><a name="item_setprog">P4::SetProg( $program_name )</a></strong>
<dd>
<p>Set the name of your script. This value is displayed in the server log
on 2004.2 or later servers.</p>
</dd>
</li>
<dt><strong><a name="item_setprotocol">P4::SetProtocol( $protflag, $value )</a></strong>
<dd>
<p>Set protocol options for this session. Deprecated. Use <a href="#item_tagged"><code>Tagged()</code></a> or
<a href="#item_parseforms"><code>ParseForms()</code></a> instead.</p>
</dd>
<dd>
<p>For example:</p>
</dd>
<dd>
<pre>
$p4->SetProtocol(tag,'');
$p4->Connect();
my @f = $p4->Fstat( "filename" );
my $c = $f[ 0 ]->{ 'clientFile' };</pre>
</dd>
</li>
<dt><strong><a name="item_setuser">P4::SetUser( $username )</a></strong>
<dd>
<p>Set your Perforce username. Defaults to:</p>
</dd>
<dd>
<pre>
1. Value from file specified by P4CONFIG
2. Value from C<$ENV{P4USER}>
3. OS username</pre>
</dd>
</li>
<dt><strong><a name="item_tag">P4::Tag()</a></strong>
<dd>
<p>Deprecated in favour of <a href="#item_tagged"><code>Tagged</code></a> (same functionality).</p>
</dd>
</li>
<dt><strong><a name="item_tagged">P4::Tagged()</a></strong>
<dd>
<p>Responses from commands that support tagged output will be returned
in the form of a hashref rather than plain text. Must be called
prior to calling <a href="#item_connect"><code>Connect()</code></a>.</p>
</dd>
</li>
<dt><strong><a name="item_warningcount">P4::WarningCount()</a></strong>
<dd>
<p>Returns the number of warnings issued by the last command.</p>
</dd>
<dd>
<pre>
$p4->WarningCount();</pre>
</dd>
</li>
<dt><strong><a name="item_warnings">P4::Warnings()</a></strong>
<dd>
<p>Returns a list of warnings from the last command</p>
</dd>
<dd>
<pre>
$p4->Warnings();</pre>
</dd>
</li>
</dl>
<p>
</p>
<hr />
<h1><a name="shortcut_methods">SHORTCUT METHODS</a></h1>
<p>The following methods are simply wrappers around the base methods
designed to make common actions easy to code.</p>
<dl>
<dt><strong><a name="item_p4_3a_3afetch_3ccmd_3e_28_29">P4::Fetch<cmd>()</a></strong>
<dd>
<p>Shorthand for running <a href="#item_run"><code>$p4->Run( "cmd", "-o" )</code></a> and returning
the results. e.g.</p>
</dd>
<dd>
<pre>
$label = $p4->FetchLabel( $labelname );
$change = $p4->FetchChange( $changeno );
$clientspec = $p4->FetchClient( $clientname );</pre>
</dd>
</li>
<dt><strong><a name="item_p4_3a_3aformat_3cspec_type_3e_28_hash__29">P4::Format<spec type>( hash )</a></strong>
<dd>
<p>Shorthand for running <code>$p4-</code>FormatSpec( <spec type>, hash )> and
returning the results. e.g.</p>
</dd>
<dd>
<pre>
$change = $p4->FetchChange();
$change->{ 'Description' } = 'Some description';
$form = $p4->FormatChange( $change );
printf( "Submitting this change:\n\n%s\n", $form );
$p4->SubmitSpec( $change );</pre>
</dd>
</li>
<dt><strong><a name="item_p4_3a_3aparse_3cspec_type_3e_28_buffer__29">P4::Parse<spec type>( buffer )</a></strong>
<dd>
<p>Shorthand for running <code>$p4-</code>ParseSpec( <spec type>, buffer )> and
returning the results. e.g.</p>
</dd>
<dd>
<pre>
$p4 = new P4;
$p4->ParseForms();
$p4->Connect() or die( "Failed to connect to server" );
$client = $p4->FetchClient(); # Returns a hashref
$client = $p4->FormatClient( $client ); # Convert to string
$client = $p4->ParseClient( $client ); # Convert back to hashref
Note that the above example is pointless, but occasionally it's useful
to be able to convert specs from hashrefs to strings and back again.</pre>
</dd>
</li>
<dt><strong><a name="item_p4_3a_3asave_3ccmd_3e_28_29">P4::Save<cmd>()</a></strong>
<dd>
<p>Shorthand for:</p>
</dd>
<dd>
<pre>
$p4->SetInput( $spec );
$p4->Run( "cmd", "-i");
e.g.</pre>
</dd>
<dd>
<pre>
$p4->SaveLabel( $label );
$p4->SaveChange( $changeno );
$p4->SaveClient( $clientspec );</pre>
</dd>
</li>
<dt><strong><a name="item_submitspec">P4::SubmitSpec()</a></strong>
<dd>
<p>Submits a changelist using the supplied change specification.
Really a shorthand for <a href="#item_setinput"><code>SetInput()</code></a> and Run( ``submit'', ``-i'' ).</p>
</dd>
<dd>
<p>For example:</p>
</dd>
<dd>
<pre>
$change = $p4->FetchChange();
$change->{ "Description" } = "some text...";
$p4->SubmitSpec( $change );</pre>
</dd>
</li>
</dl>
<p>
</p>
<hr />
<h1><a name="compatibility_with_previous_versions">COMPATIBILITY WITH PREVIOUS VERSIONS</a></h1>
<p>This version of P4 is largely backwards compatible with previous
versions with the following exceptions:</p>
<p>1. Errors and warnings are now saved in separate arrays by default. The
previous behaviour can be reinstated for those with compatibility
requirements by calling</p>
<pre>
$p4->MergeErrors( 1 );</pre>
<p>Splitting errors and warnings into separate arrays makes it easier to
ignore warnings and only have to deal with real errors.</p>
<p>2. The <code>DoPerlDiffs()</code> method in previous versions is no longer defined.
It was a legacy from an earlier release and was superceded in more recent
versions. Users who still depend on that functionality should use a 1.x
build of P4. Similarly, the corresponding <code>DoP4Diffs()</code> method is also removed.
It was likely not used and is not necessary anyway.</p>
<p>
</p>
<hr />
<h1><a name="licence">LICENCE</a></h1>
<p>Copyright (c) 1997-2007, Perforce Software, Inc. All rights reserved.</p>
<p>Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:</p>
<p>1. Redistributions of source code must retain the
above copyright notice, this list of conditions
and the following disclaimer.</p>
<p>2. Redistributions in binary form must reproduce
the above copyright notice, this list of conditions
and the following disclaimer in the documentation
and/or other materials provided with the distribution.</p>
<p>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS''
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL PERFORCE SOFTWARE, INC. BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p>
<p>
</p>
<hr />
<h1><a name="author">AUTHOR</a></h1>
<p>Tony Smith, Perforce Software ( <a href="mailto:tony@perforce.com">tony@perforce.com</a> or <a href="mailto:tony@smee.org">tony@smee.org</a> )</p>
<p>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
<p>perl(1), Perforce API documentation.</p>
</body>
</html>
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #6 | 5942 | Tony Smith | Update HTML documentation for P4Perl to latest release | ||
| #5 | 5708 | Tony Smith |
Add static P4::Identify() method to report the version of P4Perl, and the API used to build it. |
||
| #4 | 4579 | Tony Smith |
Rewrite P4Perl to be more like P4Ruby. This change does away with the old P4/P4::Client split and pulls all the functionality of P4::Client into P4. Hence P4::Client is now deprecated. There are a few gotcha's - see the Changes file, and documentation for the details, but in general it's backwards compatible. As part of this change, I'm also releasing the previous current versions of P4 and P4::Client as released versions - for posterity. P4 now gets a v3.x version number so the old versions will stand out clearly. Hopefully it's all working - works fine for me - but people should consider this a beta build, for now at least. |
||
| #3 | 2587 | Tony Smith |
Add documentation for P4::Errors() and P4::ErrorCount() which should have been there in the first place |
||
| #2 | 1733 | Tony Smith | Documentation update for P4 Perl module. | ||
| #1 | 1011 | Tony Smith |
Moved Perl API stuff one level down to make way for upcoming Ruby interface. |
||
| //guest/tony_smith/perforce/API/P4.html | |||||
| #2 | 967 | Tony Smith | Online doc update | ||
| #1 | 926 | Tony Smith |
Reorganise layout of API stuff. Current builds maintained under current/ directory, released versions under released/ . All version numbers are <major>.<changelist> so syncing to the changelist number gets you the code for that build. Also updated the index page and added HTMLised versions of the pod to make it easy to see if this is what you need. |
||