For Elan code to call an external .NET assembly, it would be necessary to write wrapper functions in C#.
However, given that Elan compiles to a .NET assembly, it should be possible for external .NET projects to call an Elan library. For example it should be possible to write a VB/C# Windows Forms or ASP.NET UI to access core functionality written in Elan.
To this end, we should consider:
Renaming the current Globalsstatic class (in the object code) to Elan (this is not visible to the Elan developer anyway)
Allowing an Elan project to not have a main. If it has no mainit cannot be run as an app - in which case the IDE will disable the Run button with a tooltip explaining why.
For Elan code to call an external .NET assembly, it would be necessary to write wrapper functions in C#.
However, given that Elan compiles to a .NET assembly, it should be possible for external .NET projects to call an Elan library. For example it should be possible to write a VB/C# Windows Forms or ASP.NET UI to access core functionality written in Elan.
To this end, we should consider:
Globalsstatic class (in the object code) toElan(this is not visible to the Elan developer anyway)mainit cannot be run as an app - in which case the IDE will disable the Run button with a tooltip explaining why.