VisualAPL: Difference between revisions
Jump to navigation
Jump to search
Miraheze>Marshall mNo edit summary |
Miraheze>Adám Brudzewsky No edit summary |
||
| Line 18: | Line 18: | ||
designed to make APL available to mainstream programmers by being fully integrated into Visual Studio, the (then) foremost IDE for .NET based development on Windows. This meant a lot of changes to traditional aspects of APL programming, like having a workspace, and avoiding all reserved words. VisualAPL supported the intermingling of C# and APL code. | designed to make APL available to mainstream programmers by being fully integrated into Visual Studio, the (then) foremost IDE for .NET based development on Windows. This meant a lot of changes to traditional aspects of APL programming, like having a workspace, and avoiding all reserved words. VisualAPL supported the intermingling of C# and APL code. | ||
Much like [[Dyalog]]'s similar project, [[APL#]], it quickly fizzled. It was released in 2009 and the last news about it were published in 2011. | Much like [[Dyalog Ltd.]]'s similar project, [[APL#]], it quickly fizzled. It was released in 2009 and the last news about it were published in 2011. | ||
== External links == | == External links == | ||
Revision as of 20:27, 28 October 2019
Visual APL, also known as APLNext, was an attempt by APLNow at creating a an implementation of based on the Microsoft .NET framework, designed to make APL available to mainstream programmers by being fully integrated into Visual Studio, the (then) foremost IDE for .NET based development on Windows. This meant a lot of changes to traditional aspects of APL programming, like having a workspace, and avoiding all reserved words. VisualAPL supported the intermingling of C# and APL code.
Much like Dyalog Ltd.'s similar project, APL#, it quickly fizzled. It was released in 2009 and the last news about it were published in 2011.