Thanks for the update.
I am delighted that APL64 will support Win32 APIs; in the next update perhaps, please include some examples of Win32 calls and how the calls are defined.
[]FMT has too much of a history and it might be better to leave it as is in order to eliminate the likelihood of breaking existing code.
A new formatting function could provide
1. The functionality of String.Format, see
https://docs.microsoft.com/en-us/dotnet ... mework-4.82. String interpolation, see
https://docs.microsoft.com/en-us/dotnet ... erpolationWith 2 above, if the fill values are arrays, I would expect the APL result to iterate. Let me explain.
- Code: Select all
Name←⊃'Ajay' 'Askoolum'
Title←⊃'Mr' 'Sir'
[]newFMT "Dear {Title} {Name}}")
should produce
Dear Mr Ajay
...
Dear Sir Askoolum
Ideally, ... will be a character of user choice with []tcff as the default. A function delivering string interpolation will make output building much (less code intensive and) more intuitive.
With 1 above, if the values are arrays, the whole array should be included. An example:
- Code: Select all
[]newFMT ('The schedule:',[]tcnl,⎕tclf),'{0},{1}' Title Name
The Schedule
Mr Ajay
Sir Askoolum
The infill variables are concatenated so that there is no need to specify their respective widths (for vertical alignment). Also, if the placeholders (i.e. {0}, {1}) specify formatting, the formatting should be applied implicitly.
I have provided a quick and rather basic response; I hope it makes sense.