All Downloads are FREE. Search and download functionalities are using the official Maven repository.

org.spongepowered.asm.mixin.injection.Inject Maven / Gradle / Ivy

Go to download

Fabric Mixin is a trait/mixin and bytecode weaving framework for Java using ASM.

The newest version!
/*
 * This file is part of Mixin, licensed under the MIT License (MIT).
 *
 * Copyright (c) SpongePowered 
 * Copyright (c) contributors
 *
 * Permission is hereby granted, free of charge, to any person obtaining a copy
 * of this software and associated documentation files (the "Software"), to deal
 * in the Software without restriction, including without limitation the rights
 * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 * copies of the Software, and to permit persons to whom the Software is
 * furnished to do so, subject to the following conditions:
 *
 * The above copyright notice and this permission notice shall be included in
 * all copies or substantial portions of the Software.
 *
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 * THE SOFTWARE.
 */
package org.spongepowered.asm.mixin.injection;

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

import org.spongepowered.asm.mixin.MixinEnvironment.Option;
import org.spongepowered.asm.mixin.injection.callback.CallbackInfo;
import org.spongepowered.asm.mixin.injection.callback.CallbackInfoReturnable;
import org.spongepowered.asm.mixin.injection.callback.LocalCapture;
import org.spongepowered.asm.mixin.injection.selectors.ITargetSelector;
import org.spongepowered.asm.mixin.injection.throwables.InjectionError;
import org.spongepowered.asm.mixin.injection.throwables.InvalidInjectionException;
import org.spongepowered.asm.util.ConstraintParser.Constraint;

/**
 * Specifies that this mixin method should inject a callback (or
 * callbacks) to itself in the target method(s) identified by
 * {@link #method}.
 * 
 * 

Callbacks are simple injectors which simply inject a call to the decorated * method (the handler) in the target method (or methods) * selected by the selectors specified in {@link #method}. Callback Injectors * can also capture arguments and local variables from the target for * use in the handler.

* *

Callback handler methods should always return void and should * have the same static-ness as their target (though it is allowable to * have a static callback injected into an instance method, and for * obvious reasons the inverse is not permitted).

* *

Basic usage

* *

The simplest usage of @Inject captures no context from the * target scope. This is particularly useful if the injector is targetting * multiple methods with different signatures. In this case only the * {@link CallbackInfo} (or {@link CallbackInfoReturnable} as appropriate) is * required.

* *
private void onSomeEvent(CallbackInfo ci)
* *

Capture target arguments

* *

Callbacks can also capture the arguments passed to the target method. To * do so specify the target arguments before the {@link CallbackInfo}:

* *
private void onSomeEvent(int arg1, String arg2, * CallbackInfo ci)
* *

Surrogate methods

* *

If injecting into multiple methods with different target arguments it is * obviously possible to ignore the target arguments (see "Basic Usage" above) * but this may be unsuitable if arguments from the target are required. If you * need to inject into multiple methods but also wish to capture method * arguments you may provide a surrogate method with the alternative * signature. In fact you may provide as many surrogates as required by the * injection. Surrogate methods much have the same name as the handler method * and must be decorated with {@link Surrogate}. A surrogate may also be * required where the LVT of a method with local capture (see below) is * known to change between different environments or injection points.

* *

Capture local variables

* *

In addition to capturing the target method arguments, it may be desirable * to capture locally-scoped variables from the target method at the point of * injection. This is usually executed in two stages:

* *
    *
  1. Set the {@link #locals()} value of your injection to * {@link LocalCapture#PRINT} and run the application.
  2. *
  3. When the injector is processed, a listing of the LVT is produced * accompanied by a generated signature for your handler method including * the discovered args. Modify your handler signature accordingly.
  4. *
* *

For more details see {@link #locals()}.

* */ @Target({ ElementType.METHOD }) @Retention(RetentionPolicy.RUNTIME) public @interface Inject { /** * The identifier for this injector, can be retrieved via the * {@link CallbackInfo#getId} accessor. If not specified, the ID defaults to * the target method name. * * @return the injector id to use */ public String id() default ""; /** * String representation of one or more * {@link ITargetSelector target selectors} which identify the target * methods. * * @return target method(s) for this injector */ public String[] method() default {}; /** * Literal representation of one or more {@link Desc @Desc} annotations * which identify the target methods. * * @return target method(s) for this injector as descriptors */ public Desc[] target() default {}; /** * Array of {@link Slice} annotations which describe the method bisections * used in the {@link #at} queries for this injector. * * @return slices */ public Slice[] slice() default {}; /** * Array of {@link At} annotations which describe the * {@link InjectionPoint}s in the target method. Allows one or more * callbacks to be injected in the target method. * * @return injection point specifiers for this injector */ public At[] at(); /** * Setting an injected callback to cancellable allows the injected * callback to inject optional RETURN opcodes into the target method, the * return behaviour can then be controlled from within the callback by * interacting with the supplied {@link CallbackInfo} object. * * @return true if this injector should inject appropriate RETURN opcodes * which allow it to be cancelled */ public boolean cancellable() default false; /** * Specifies the local variable capture behaviour for this injector. * *

When capturing local variables in scope, the variables are appended to * the callback invocation after the {@link CallbackInfo} argument.

* *

Capturing local variables from the target scope requires careful * planning because unlike other aspects of an injection (such as the target * method name and signature), the local variable table is not safe * from modification by other transformers which may be in use in the * production environment. Even other injectors which target the same target * method have the ability to modify the local variable table and thus it is * in no way safe to assume that local variables in scope at development * time will be so in production.

* *

To provide some level of flexibility, especially where changes can be * anticipated (for example a well-known mod makes changes which result in a * particular structure for the local variable table) it is possible to * provide overloads for the handler method which will become * surrogate targets for the orphaned injector by annotating them with an * {@link Surrogate} annotation.

* *

You can improve the robustness of your local capture injection by only * specifying locals up to the last variable you wish to use. For example if * the target LVT contains <int, int, int, float, String> and * you only need the float value, you can choose to omit the unused * String and changes to the LVT beyond that point will not affect * your injection.

* *

It is also important to nominate the failure behaviour to follow when * local capture fails and so all {@link LocalCapture} behaviours which * specify a capture action imply a particular behaviour for handling * failure. See the javadoc on the {@link LocalCapture} members for more * details.

* *

Determining what local variables are available to you and in what * order can be somewhat tricky, and so a simple mechanism for enumerating * available locals is provided. By setting locals to * {@link LocalCapture#PRINT}, the injector writes the local capture state * to STDERR instead of injecting the callback. Using the output thus * obtained it is then a straightforward matter of altering the callback * method signature to match the signature proposed by the Callback * Injector.

* * @return the desired local capture behaviour for this injector */ public LocalCapture locals() default LocalCapture.NO_CAPTURE; /** * By default, the annotation processor will attempt to locate an * obfuscation mapping for all {@link Inject} methods since it is * anticipated that in general the target of a {@link Inject} annotation * will be an obfuscated method in the target class. However since it is * possible to also apply mixins to non-obfuscated targets (or non- * obfuscated methods in obfuscated targets, such as methods added by Forge) * it may be necessary to suppress the compiler error which would otherwise * be generated. Setting this value to false will cause the * annotation processor to skip this annotation when attempting to build the * obfuscation table for the mixin. * * @return True to instruct the annotation processor to search for * obfuscation mappings for this annotation */ public boolean remap() default true; /** * In general, injectors are intended to "fail soft" in that a failure to * locate the injection point in the target method is not considered an * error condition. Another transformer may have changed the method * structure or any number of reasons may cause an injection to fail. This * also makes it possible to define several injections to achieve the same * task given expected mutation of the target class and the * injectors which fail are simply ignored. * *

However, this behaviour is not always desirable. For example, if your * application depends on a particular injection succeeding you may wish to * detect the injection failure as an error condition. This argument is thus * provided to allow you to stipulate a minimum number of successful * injections for this callback handler. If the number of injections * specified is not achieved then an {@link InjectionError} is thrown at * application time. Use this option with care.

* * @return Minimum required number of injected callbacks, default specified * by the containing config */ public int require() default -1; /** * Like {@link #require()} but only enabled if the * {@link Option#DEBUG_INJECTORS mixin.debug.countInjections} option is set * to true and defaults to 1. Use this option during debugging to * perform simple checking of your injectors. Causes the injector to throw * a {@link InvalidInjectionException} if the expected number of injections * is not realised. * * @return Minimum number of expected callbacks, default 1 */ public int expect() default 1; /** * Injection points are in general expected to match every candidate * instruction in the target method or slice, except in cases where options * such as {@link At#ordinal} are specified which naturally limit the number * of results. * *

This option allows for sanity-checking to be performed on the results * of an injection point by specifying a maximum allowed number of matches, * similar to that afforded by {@link Group#max}. For example if your * injection is expected to match 4 invocations of a target method, but * instead matches 5, this can become a detectable tamper condition by * setting this value to 4. * *

Setting any value 1 or greater is allowed. Values less than 1 or less * than {@link #require} are ignored. {@link #require} supercedes this * argument such that if allow is less than require the * value of require is always used.

* *

Note that this option is not a limit on the query behaviour of * this injection point. It is only a sanity check used to ensure that the * number of matches is not too high * * @return Maximum allowed number of injections for this */ public int allow() default -1; /** * Returns constraints which must be validated for this injector to * succeed. See {@link Constraint} for details of constraint formats. * * @return Constraints for this annotation */ public String constraints() default ""; /** * By default almost all injectors for a target class apply their injections * at the same time. In other words, if multiple mixins target the same * class then injectors are applied in priority order (since the mixins * themselves are merged in priority order, and injectors run in the order * they were merged). The exception being redirect injectors, which apply in * a later pass. * *

The default order for injectors is 1000, and redirect * injectors use 10000.

* *

Specifying a value for order alters this default behaviour * and causes the injector to inject either earlier or later than it * normally would. For example specifying 900 will cause the * injector to apply before others, while 1100 will apply later. * Injectors with the same order will still apply in order of their * mixin's priority. * * @return the application order for this injector, uses DEFAULT (1000) if * not specified */ public int order() default 1000; }





© 2015 - 2024 Weber Informatics LLC | Privacy Policy