APL Wiki|
Size: 1717
Comment:
|
Size: 1712
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| = APL Application Programming Library (APLAPL) = | = APL Application Programming Library (APL) = |
| Line 13: | Line 13: |
| ##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||'''Needs .NET'''|| ||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''No'''|| |
##||||||<tablestyle="background:#ffe; padding:0 2em 1em 0;">''''''||''''''|| ||'''Name'''||'''Description'''||'''Type'''||'''Originator'''||'''Needs .NET'''|| |
APL Application Programming Library (APL)
At the time being, everything here refers to Dyalog APL. That might change sometime, but as long as no other stuff turns up here it keeps things simple.
All classes published here must be part of "The Open Source APL Project" in short [:OpenSourceAplProject:TOSAP]. Yes, classes, so it has to be at least version 11 of Dyalog APL you are working with.
The idea behind TOSAP is to provide classes ready for usage for every-day-problems programmers typically come across.
Many but not all classes do not use .NET at all. That might look strange: there are tons of useful .NET classes available, and they are free, so why not using them? Well, it all depends. Try to get a directory listing of a directory which contains 100,000 files and you know what I mean.
Name |
Description |
Type |
Originator |
Needs .NET |
[:APLTeamsUtil:APLTeamsUtil] |
General utilities |
Dyalog |
APL Team |
No |
[:ADOC:ADOC] |
Automated Documentation Generation |
Dyalog |
APL Team |
No |
[:Hash:Hash] |
Managing key/value-pairs |
Dyalog |
APL Team |
No |
Dealing with INI files |
Dyalog |
APL Team |
No |
|
[:Logger:Logger] |
Writing Log Files |
Dyalog |
APL Team |
No |
Dealing with the Windows Event Log |
Dyalog |
APL Team |
Yes |
|
[:WinFile:WinFile] |
Dealing with files and directories |
Dyalog |
APL Team |
No |
[:WinReg:WinReg] |
Dealing with the Windows Registry |
Dyalog |
APL Team |
No |