Index operator []

This article shows usage of [] operator for arrays and collections. In Javonet, every array or collection from called technology is treated as a reference.

Javonet allows you to reference and use modules or packages written in (Java/Kotlin/Groovy/Clojure, C#/VB.NET, Ruby, Perl, Python, JavaScript/TypeScript) like they were created in your technology. If have not yet created your first project check Javonet overview and quick start guides for your technology.

With Javonet you can interact with arrays from .NET Framework DLL like they were available in any language but invocation must be performed through Javonet SDK API.

Custom .NET Framework DLL with arrays handling

With Javonet it is possible to reference any custom .NET Framework DLL and interact with arrays declared on types defined within that module almost the same as with any other any language library.

Snippet below represents the sample code from .NET Framework DLL that has methods which return or process the arrays:

public string[] Get1DArray()
{
	return new string[] { "one", "two", "three", "four", "five" };
}

public string[,] Get2DArray()
{
	return new string[,] { { "S00", "S01" }, { "S10", "S11" } };
}

public double AddArrayElementsAndMultiply(double[] myArray, double myValue)
{
	double sum = 0;
	foreach (double element in myArray)
	{
		sum += element;
	}

	return sum * myValue;
}

Each array or collection from .NET Framework DLL returns as InvocationContext which contains reference to the target data. Javonet SDK implements [] operator on InvocationContext to interact with complex data objects in any language:

Get element

I code in:

Select language you code in:

In the snippet above, get1DArray method is used to get reference to 1D array from .NET Framework DLL. Operator [] is used to get element from the array.

Set element

I code in:

Select language you code in:

In the snippet above, get1DArray method is used to get reference to 1D array from .NET Framework DLL. Operator [] is used to set element of the 1D array.

The same operation can be performed remotely by just changing the new Runtime Context invocation from in memory to tcp that will create and interact with your .NET Framework DLL objects on any remote node, container or service that hosts Javonet Code Gateway. This way you can preserve the same logic in your application and instantly switch between monolithic and microservices architecture without the need to implement the integration layer based on web services or other remote invocation methods.

Read more about use cases and software architecture scenarios where Javonet runtime bridging technology can support your development process.