Change order of outpoint printing to be more consistent with Bitcoin practice

This commit is contained in:
Mike Hearn 2012-02-09 16:14:29 +01:00
parent 9ba77a0d68
commit 23279aff5f

View file

@ -69,15 +69,11 @@ public class TransactionOutPoint extends ChildMessage implements Serializable {
/**
* Deserializes the message. This is usually part of a transaction message.
* @param params NetworkParameters object.
* @param msg Bitcoin protocol formatted byte array containing message content.
* @param offset The location of the first msg byte within the array.
* @param protocolVersion Bitcoin protocol version.
* @param parseLazy Whether to perform a full parse immediately or delay until a read is requested.
* @param parseRetain Whether to retain the backing byte array for quick reserialization.
* If true and the backing byte array is invalidated due to modification of a field then
* the cached bytes may be repopulated and retained if the message is serialized again in the future.
* @param length The length of message if known. Usually this is provided when deserializing of the wire
* as the length will be provided as part of the header. If unknown then set to Message.UNKNOWN_LENGTH
* @throws ProtocolException
*/
public TransactionOutPoint(NetworkParameters params, byte[] payload, int offset, Message parent, boolean parseLazy, boolean parseRetain) throws ProtocolException {
@ -137,7 +133,7 @@ public class TransactionOutPoint extends ChildMessage implements Serializable {
@Override
public String toString() {
return "outpoint " + index + ":" + hash.toString();
return "outpoint " + hash.toString() + ":" + index;
}