Nested function: Difference between revisions

From Rosetta Code
Content added Content deleted
(Added R. Rather short.)
m (→‎{{header|Wren}}: Changed to Wren S/H)
 
(24 intermediate revisions by 15 users not shown)
Line 24: Line 24:
{{trans|Python}}
{{trans|Python}}


<lang 11l>F makeList(separator)
<syntaxhighlight lang="11l">F makeList(separator)
V counter = 1
V counter = 1


Line 34: Line 34:
R makeItem(‘first’)‘’makeItem(‘second’)‘’makeItem(‘third’)
R makeItem(‘first’)‘’makeItem(‘second’)‘’makeItem(‘third’)


print(makeList(‘. ’))</lang>
print(makeList(‘. ’))</syntaxhighlight>


{{out}}
{{out}}
Line 44: Line 44:


=={{header|Ada}}==
=={{header|Ada}}==
<lang Ada>with Ada.Text_IO;
<syntaxhighlight lang="ada">with Ada.Text_IO;


procedure Nested_Functions is -- 'Nested_Functions' is the name of 'main'
procedure Nested_Functions is -- 'Nested_Functions' is the name of 'main'
Line 67: Line 67:
Ada.Text_IO.Put_Line(Item);
Ada.Text_IO.Put_Line(Item);
end loop;
end loop;
end Nested_Functions;</lang>
end Nested_Functions;</syntaxhighlight>
{{out}}
{{out}}
<pre>$ ./nested_functions
<pre>$ ./nested_functions
Line 73: Line 73:
2. Second
2. Second
3. Third
3. Third
</pre>
=={{header|68000 Assembly}}==
<syntaxhighlight lang="68000devpac">;program starts here, after loading palettes etc.
MOVE.W #3,D1
MOVE.W #'.',D4

JSR MakeList

jmp * ;halt



MakeList:
MOVE.W #1,D0
loop_MakeList:
MOVE.W D0,-(SP)
JSR PrintHex
MOVE.B D4,D0 ;load separator into D0
JSR PrintChar
MOVE.B #' ',D0
JSR PrintChar
MOVE.W (SP)+,D0
JSR MakeItem
CMP.W D0,D1
BCC loop_MakeList ;back to start
RTS
MakeItem:
MOVE.W D0,D2
SUBQ.W #1,D2
LSL.W #2,D2
LEA PointerToText,A0
MOVE.L (A0,D2),A3
JSR PrintString
JSR NewLine
ADDQ.W #1,D0
RTS


PointerToText:
DC.L FIRST,SECOND,THIRD
FIRST:
DC.B "FIRST",0
EVEN
SECOND:
DC.B "SECOND",0
EVEN
THIRD:
DC.B "THIRD",0
EVEN</syntaxhighlight>

{{out}}
[https://ibb.co/mqCKVGy Output running on MAME]

Also displayed here:
<pre>
01. FIRST
02. SECOND
03. THIRD
</pre>
</pre>


=={{header|ALGOL 68}}==
=={{header|ALGOL 68}}==
<lang algol68>PROC make list = ( STRING separator )STRING:
<syntaxhighlight lang="algol68">PROC make list = ( STRING separator )STRING:
BEGIN
BEGIN
INT counter := 0;
INT counter := 0;
Line 88: Line 149:


print( ( make list( ". " ) ) )
print( ( make list( ". " ) ) )
</syntaxhighlight>
</lang>


=={{header|ALGOL W}}==
=={{header|ALGOL W}}==
Algol W strings are fixed length which makes this slightly more complicated than the Algol 68 solution.
Algol W strings are fixed length which makes this slightly more complicated than the Algol 68 solution.
<lang algolw>begin
<syntaxhighlight lang="algolw">begin
string(30) procedure makeList ( string(2) value separator ) ;
string(30) procedure makeList ( string(2) value separator ) ;
begin
begin
Line 116: Line 177:
end; % makeList %
end; % makeList %
write( makeList( ". " ) )
write( makeList( ". " ) )
end.</lang>
end.</syntaxhighlight>


=={{header|AppleScript}}==
=={{header|AppleScript}}==
<lang AppleScript>--------------------- NESTED FUNCTION --------------------
<syntaxhighlight lang="applescript">--------------------- NESTED FUNCTION --------------------


-- makeList :: String -> String
-- makeList :: String -> String
Line 172: Line 233:
return lst
return lst
end tell
end tell
end map</lang>
end map</syntaxhighlight>
{{Out}}
{{Out}}
<pre>1. first
<pre>1. first
Line 181: Line 242:
Note, however, that mutation creates redundant complexity and loss of referential transparency. Functions which modify values outside their own scope are rarely, if ever, necessary, and always best avoided. Simpler and sounder here to derive the incrementing index either by zipping the input list with a range of integers, or by inheriting it from the higher order map function:
Note, however, that mutation creates redundant complexity and loss of referential transparency. Functions which modify values outside their own scope are rarely, if ever, necessary, and always best avoided. Simpler and sounder here to derive the incrementing index either by zipping the input list with a range of integers, or by inheriting it from the higher order map function:


<lang AppleScript>-- makeList :: String -> String
<syntaxhighlight lang="applescript">-- makeList :: String -> String
on makeList(separator)
on makeList(separator)
Line 192: Line 253:
map(makeItem, ["first", "second", "third"]) as string
map(makeItem, ["first", "second", "third"]) as string
end makeList</lang>
end makeList</syntaxhighlight>


=={{header|Arturo}}==
=={{header|Arturo}}==
<lang rebol>makeList: function [separator][
<syntaxhighlight lang="rebol">makeList: function [separator][
counter: 1
counter: 1


Line 211: Line 272:
]
]


print join.with:"\n" makeList ". "</lang>
print join.with:"\n" makeList ". "</syntaxhighlight>


{{out}}
{{out}}
Line 220: Line 281:


=={{header|ATS}}==
=={{header|ATS}}==
<syntaxhighlight lang="ats">
<lang ATS>
(* ****** ****** *)
(* ****** ****** *)
//
//
Line 258: Line 319:


(* ****** ****** *)
(* ****** ****** *)
</syntaxhighlight>
</lang>

=={{header|BQN}}==
<syntaxhighlight lang="bqn">MakeList ← {
nl←@+10 ⋄ s←𝕩 ⋄ i←0
MakeItem ← {i+↩1 ⋄ (•Fmt i)∾s∾𝕩}
(⊣∾nl∾⊢)´MakeItem¨"first"‿"second"‿"third"
}</syntaxhighlight>

{{out}}
<pre>
MakeList ". "
"1. first
2. second
3. third"
</pre>


=={{header|C}}==
=={{header|C}}==
Line 267: Line 343:


'''IMPORTANT''' This implementation will only work with GCC. Go through the link above for details.
'''IMPORTANT''' This implementation will only work with GCC. Go through the link above for details.
<syntaxhighlight lang="c">
<lang C>
#include<stdlib.h>
#include<stdlib.h>
#include<stdio.h>
#include<stdio.h>
Line 305: Line 381:
return 0;
return 0;
}
}
</syntaxhighlight>
</lang>
Output:
Output:
<pre>
<pre>
Line 314: Line 390:


=={{header|C sharp|C#}}==
=={{header|C sharp|C#}}==
<lang csharp>string MakeList(string separator)
<syntaxhighlight lang="csharp">string MakeList(string separator)
{
{
int counter = 1;
int counter = 1;
Line 323: Line 399:
}
}


Console.WriteLine(MakeList(". "));</lang>
Console.WriteLine(MakeList(". "));</syntaxhighlight>
'''Update'''<br/>
'''Update'''<br/>
As of C#7, we can nest actual methods inside other methods instead of creating delegate instances. They can even be declared after the return statement.
As of C#7, we can nest actual methods inside other methods instead of creating delegate instances. They can even be declared after the return statement.
<lang csharp>string MakeList2(string separator)
<syntaxhighlight lang="csharp">string MakeList2(string separator)
{
{
int counter = 1;
int counter = 1;
Line 333: Line 409:
//using string interpolation
//using string interpolation
string MakeItem(string item) => $"{counter++}{separator}{item}\n";
string MakeItem(string item) => $"{counter++}{separator}{item}\n";
}</lang>
}</syntaxhighlight>


=={{header|C++}}==
=={{header|C++}}==
{{works with|C++11}}
{{works with|C++11}}
<lang cpp>#include <iostream>
<syntaxhighlight lang="cpp">#include <iostream>
#include <string>
#include <string>
#include <vector>
#include <vector>
Line 352: Line 428:
for (auto item : makeList(". "))
for (auto item : makeList(". "))
std::cout << item << "\n";
std::cout << item << "\n";
}</lang>
}</syntaxhighlight>


=={{header|Clojure}}==
=={{header|Clojure}}==


<lang clojure>(defn make-list [separator]
<syntaxhighlight lang="clojure">(defn make-list [separator]
(let [x (atom 0)]
(let [x (atom 0)]
(letfn [(make-item [item] (swap! x inc) (println (format "%s%s%s" @x separator item)))]
(letfn [(make-item [item] (swap! x inc) (println (format "%s%s%s" @x separator item)))]
Line 363: Line 439:
(make-item "third"))))
(make-item "third"))))


(make-list ". ")</lang>
(make-list ". ")</syntaxhighlight>


{{out}}
{{out}}
Line 374: Line 450:
=={{header|Common Lisp}}==
=={{header|Common Lisp}}==


<lang lisp>(defun my-make-list (separator)
<syntaxhighlight lang="lisp">(defun my-make-list (separator)
(let ((counter 0))
(let ((counter 0))
(flet ((make-item (item)
(flet ((make-item (item)
Line 383: Line 459:
(make-item "third")))))
(make-item "third")))))


(format t (my-make-list ". "))</lang>
(format t (my-make-list ". "))</syntaxhighlight>


''PS: A function named make-list is already defined in Common Lisp, see [http://www.lispworks.com/documentation/HyperSpec/Body/f_mk_lis.htm#make-list specification].''
''PS: A function named make-list is already defined in Common Lisp, see [http://www.lispworks.com/documentation/HyperSpec/Body/f_mk_lis.htm#make-list specification].''


=={{header|Cowgol}}==
=={{header|Cowgol}}==
<lang cowgol>include "cowgol.coh";
<syntaxhighlight lang="cowgol">include "cowgol.coh";
include "strings.coh";
include "strings.coh";


Line 418: Line 494:
var buffer: uint8[100];
var buffer: uint8[100];


print(MakeList(". ", &buffer as [uint8]));</lang>
print(MakeList(". ", &buffer as [uint8]));</syntaxhighlight>


{{out}}
{{out}}
Line 428: Line 504:
=={{header|D}}==
=={{header|D}}==


<lang d>string makeList(string seperator) {
<syntaxhighlight lang="d">string makeList(string seperator) {
int counter = 1;
int counter = 1;


Line 442: Line 518:
import std.stdio : writeln;
import std.stdio : writeln;
writeln(makeList(". "));
writeln(makeList(". "));
}</lang>
}</syntaxhighlight>

{{out}}

<pre>1. first
2. second
3. third</pre>


=={{header|Delphi}}==
=={{header|Delphi}}==
''See [[#Pascal|Pascal]]''
''See [[#Pascal|Pascal]]''

=={{header|Ecstasy}}==
<syntaxhighlight lang="java">
module NestedFunction {
static String makeList(String separator) {
Int counter = 1;

function String(String) makeItem = item -> $"{counter++}{separator}{item}\n";

return makeItem("first")
+ makeItem("second")
+ makeItem("third");
}

void run() {
@Inject Console console;
console.print(makeList(". "));
}
}
</syntaxhighlight>

{{out}}
<pre>
1. first
2. second
3. third
</pre>


=={{header|Elena}}==
=={{header|Elena}}==
ELENA 5.0 :
ELENA 6.x :
<lang elena>import extensions;
<syntaxhighlight lang="elena">import extensions;
MakeList(separator)
MakeList(separator)
Line 455: Line 564:
var counter := 1;
var counter := 1;
var makeItem := (item){ var retVal := counter.toPrintable() + separator + item + (forward newLine); counter += 1; ^ retVal };
var makeItem := (item){ var retVal := counter.toPrintable() + separator + item + newLineConstant; counter += 1; ^ retVal };
^ makeItem("first") + makeItem("second") + makeItem("third")
^ makeItem("first") + makeItem("second") + makeItem("third")
Line 463: Line 572:
{
{
console.printLine(MakeList(". "))
console.printLine(MakeList(". "))
}</lang>
}</syntaxhighlight>
{{out}}
{{out}}
<pre>
<pre>
Line 473: Line 582:
=={{header|Elixir}}==
=={{header|Elixir}}==
Elixir data are immutable. Anonymous functions are closures and as such they can access variables that are in scope when the function is defined. Keep in mind a variable assigned inside a function does not affect its surrounding environment:
Elixir data are immutable. Anonymous functions are closures and as such they can access variables that are in scope when the function is defined. Keep in mind a variable assigned inside a function does not affect its surrounding environment:
<lang elixir>defmodule Nested do
<syntaxhighlight lang="elixir">defmodule Nested do
def makeList(separator) do
def makeList(separator) do
counter = 1
counter = 1
Line 487: Line 596:
end
end


IO.write Nested.makeList(". ")</lang>
IO.write Nested.makeList(". ")</syntaxhighlight>


{{out}}
<pre>
1. first
2. second
3. third
</pre>

=={{header|EMal}}==
<syntaxhighlight lang="emal">
fun makeList = List by text separator
int counter = 0
fun makeItem = text by text item
return ++counter + separator + item
end
return text[makeItem("first"), makeItem("second"), makeItem("third")]
end
for each text item in makeList(". ") do writeLine(item) end
</syntaxhighlight>
{{out}}
{{out}}
<pre>
<pre>
Line 501: Line 628:
If we really wanted, we could also define a named word inside <code>make-list</code> at run time, using words such as <code>define</code> in the <code>words</code> vocabulary.
If we really wanted, we could also define a named word inside <code>make-list</code> at run time, using words such as <code>define</code> in the <code>words</code> vocabulary.


<lang factor>USING: io kernel math math.parser locals qw sequences ;
<syntaxhighlight lang="factor">USING: io kernel math math.parser locals qw sequences ;
IN: rosetta-code.nested-functions
IN: rosetta-code.nested-functions


Line 513: Line 640:
;
;
". " make-list write</lang>
". " make-list write</syntaxhighlight>


=={{header|Fortran}}==
=={{header|Fortran}}==
===Arithmetic statement functions===
===Arithmetic statement functions===
Fortran allows the user to define functions (and subroutines also) but from first Fortran (1958) on these are compiled as separate items and cannot themselves contain the definition of another function (or subroutine) - except for the special form allowing the definition of what is called an arithmetic statement function, such as follows:<lang Fortran> FUNCTION F(X)
Fortran allows the user to define functions (and subroutines also) but from first Fortran (1958) on these are compiled as separate items and cannot themselves contain the definition of another function (or subroutine) - except for the special form allowing the definition of what is called an arithmetic statement function, such as follows:<syntaxhighlight lang="fortran"> FUNCTION F(X)
REAL X
REAL X
DIST(U,V,W) = X*SQRT(U**2 + V**2 + W**2) !The contained function.
DIST(U,V,W) = X*SQRT(U**2 + V**2 + W**2) !The contained function.
T = EXP(X)
T = EXP(X)
F = T + DIST(T,SIN(X),ATAN(X) + 7) !Invoked...
F = T + DIST(T,SIN(X),ATAN(X) + 7) !Invoked...
END</lang>
END</syntaxhighlight>
This (deranged) function contains within it the definition of function DIST (which must be achieved in a single arithmetic statement), and which has access to all the variables of its containing function as well as its own parameters. The sequence <code>DIST(U,V,W) = ''etc.''</code> would normally be interpreted as an assignment of a value to an element of an array called DIST, but, no such array has been declared so this must therefore be the definition of an arithmetic statement function. Such functions are defined following any declarations of variables, and precede the normal executable statements such as <code>T = EXP(X)</code>. Since they are for arithmetic they cannot be used for character manipulations, and the CHARACTER variable only appeared with F77.
This (deranged) function contains within it the definition of function DIST (which must be achieved in a single arithmetic statement), and which has access to all the variables of its containing function as well as its own parameters. The sequence <code>DIST(U,V,W) = ''etc.''</code> would normally be interpreted as an assignment of a value to an element of an array called DIST, but, no such array has been declared so this must therefore be the definition of an arithmetic statement function. Such functions are defined following any declarations of variables, and precede the normal executable statements such as <code>T = EXP(X)</code>. Since they are for arithmetic they cannot be used for character manipulations, and the CHARACTER variable only appeared with F77.


Line 528: Line 655:
With the advent of F90 comes the CONTAINS statement, whereby within a function (or subroutine) but oddly, at its ''end'' (but before its END) appears the key word CONTAINS, after which further functions (and subroutines) may be defined in the established manner. These have access to all the variables defined in the containing routine, though if the contained routine declares a name used in the containing routine then that outside name becomes inaccessible.
With the advent of F90 comes the CONTAINS statement, whereby within a function (or subroutine) but oddly, at its ''end'' (but before its END) appears the key word CONTAINS, after which further functions (and subroutines) may be defined in the established manner. These have access to all the variables defined in the containing routine, though if the contained routine declares a name used in the containing routine then that outside name becomes inaccessible.


Such contained routines are not themselves allowed to contain routines, so that the nesting is limited to two levels - except that arithmetic statement functions are available, so that three levels could be employed. Languages such as Algol, pl/i, Pascal, etc. impose no such constraint. <lang Fortran> SUBROUTINE POOBAH(TEXT,L,SEP) !I've got a little list!
Such contained routines are not themselves allowed to contain routines, so that the nesting is limited to two levels - except that arithmetic statement functions are available, so that three levels could be employed. Languages such as Algol, pl/i, Pascal, etc. impose no such constraint. <syntaxhighlight lang="fortran"> SUBROUTINE POOBAH(TEXT,L,SEP) !I've got a little list!
CHARACTER*(*) TEXT !The supplied scratchpad.
CHARACTER*(*) TEXT !The supplied scratchpad.
INTEGER L !Its length.
INTEGER L !Its length.
Line 560: Line 687:
CALL POOBAH(TEXT,L,". ")
CALL POOBAH(TEXT,L,". ")
WRITE (6,"(A)") TEXT(1:L)
WRITE (6,"(A)") TEXT(1:L)
END</lang>
END</syntaxhighlight>


Fortran doesn't offer a "list" construction as a built-in facility so it seemed easiest to prepare the list in a CHARACTER variable. These do not have a length attribute as in a string, the LEN function reports the size of the character variable not something such as the current length of a string varying from zero to the storage limit. So, the length of the in-use portion is tracked with the aid of an auxiliary variable, and one must decide on a sufficiently large scratchpad area to hold the anticipated result. And, since the items are of varying length, the length of the whole sequence is returned, not the number of items. Subroutine POOBAH could be instead a function, but, it would have to return a fixed-size result (as in say <code>CHARACTER*66 FUNCTION POOBAH(SEP)</code>) and can't return a length as well, unless via messing with a global variable such as in COMMON or via an additional parameter as with the L above.
Fortran doesn't offer a "list" construction as a built-in facility so it seemed easiest to prepare the list in a CHARACTER variable. These do not have a length attribute as in a string, the LEN function reports the size of the character variable not something such as the current length of a string varying from zero to the storage limit. So, the length of the in-use portion is tracked with the aid of an auxiliary variable, and one must decide on a sufficiently large scratchpad area to hold the anticipated result. And, since the items are of varying length, the length of the whole sequence is returned, not the number of items. Subroutine POOBAH could be instead a function, but, it would have to return a fixed-size result (as in say <code>CHARACTER*66 FUNCTION POOBAH(SEP)</code>) and can't return a length as well, unless via messing with a global variable such as in COMMON or via an additional parameter as with the L above.
Line 569: Line 696:


===When storage is abundant===
===When storage is abundant===
Another way of providing a "list" is via an array as in <code>CHARACTER*28 TEXT(9)</code>) so that each item occupied one element, and the maddening question "how long is a piece of string" arises twice: how much storage to allow for each element when all must be as long as the longest text expected, and, how many elements are to be allowed for.<lang Fortran> SUBROUTINE POOBAH(TEXT,N,SEP) !I've got a little list!
Another way of providing a "list" is via an array as in <code>CHARACTER*28 TEXT(9)</code>) so that each item occupied one element, and the maddening question "how long is a piece of string" arises twice: how much storage to allow for each element when all must be as long as the longest text expected, and, how many elements are to be allowed for.<syntaxhighlight lang="fortran"> SUBROUTINE POOBAH(TEXT,N,SEP) !I've got a little list!
CHARACTER*(*) TEXT(*) !The supplied scratchpad.
CHARACTER*(*) TEXT(*) !The supplied scratchpad.
INTEGER N !Entry count.
INTEGER N !Entry count.
Line 591: Line 718:
CALL POOBAH(TEXT,N,". ")
CALL POOBAH(TEXT,N,". ")
WRITE (6,"(A)") (TEXT(I)(1:LEN_TRIM(TEXT(I))), I = 1,N)
WRITE (6,"(A)") (TEXT(I)(1:LEN_TRIM(TEXT(I))), I = 1,N)
END</lang>
END</syntaxhighlight>
The output statement could be <code>WRITE (6,"(A)") TEXT(1:N)</code> but this would write out the trailing spaces in each element. A TRIM intrinsic function may be available, but, leading spaces may be desired in the case that there are to be more than nine elements. If so, <code>FORMAT (I2,2A)</code> would be needed up to ninety-nine, or more generally, I0 format. Except that would not write out leading spaces and would spoil the neatness of a columnar layout. With file names, the lack of leading spaces (or zero digits) leads to the ideas explored in [[Natural_sorting|"Natural" sorting]]. One could define constants via the PARAMETER statement to document the linkage between the number of array elements and the correct FORMAT code, though this is messy because for NMAX elements the format code requires <Log10(NMAX) + 1> digits, and in such an attempt I've seen Log10(10) come out not as one but as 0·9999932 or somesuch, truncating to zero.
The output statement could be <code>WRITE (6,"(A)") TEXT(1:N)</code> but this would write out the trailing spaces in each element. A TRIM intrinsic function may be available, but, leading spaces may be desired in the case that there are to be more than nine elements. If so, <code>FORMAT (I2,2A)</code> would be needed up to ninety-nine, or more generally, I0 format. Except that would not write out leading spaces and would spoil the neatness of a columnar layout. With file names, the lack of leading spaces (or zero digits) leads to the ideas explored in [[Natural_sorting|"Natural" sorting]]. One could define constants via the PARAMETER statement to document the linkage between the number of array elements and the correct FORMAT code, though this is messy because for NMAX elements the format code requires <Log10(NMAX) + 1> digits, and in such an attempt I've seen Log10(10) come out not as one but as 0·9999932 or somesuch, truncating to zero.


Line 597: Line 724:


=={{header|Free Pascal}}==
=={{header|Free Pascal}}==
<lang pascal>// In Pascal, functions always _have_ to return _some_ value,
<syntaxhighlight lang="pascal">// In Pascal, functions always _have_ to return _some_ value,
// but the the task doesn’t specify what to return.
// but the the task doesn’t specify what to return.
// Hence makeList and makeItem became procedures.
// Hence makeList and makeItem became procedures.
Line 634: Line 761:
makeItem;
makeItem;
makeItem;
makeItem;
end;</lang>
end;</syntaxhighlight>


=={{header|FreeBASIC}}==
=={{header|FreeBASIC}}==
Line 642: Line 769:
by reference to the second procedure so it can be modified by the latter.
by reference to the second procedure so it can be modified by the latter.


<lang freebasic>' FB 1.05.0 Win64
<syntaxhighlight lang="freebasic">' FB 1.05.0 Win64


Sub makeItem(sep As String, ByRef counter As Integer, text As String)
Sub makeItem(sep As String, ByRef counter As Integer, text As String)
Line 661: Line 788:
Print "Press any key to quit"
Print "Press any key to quit"
Sleep
Sleep
</syntaxhighlight>
</lang>


{{out}}
{{out}}
Line 672: Line 799:
=={{header|Fōrmulæ}}==
=={{header|Fōrmulæ}}==


{{FormulaeEntry|page=https://formulae.org/?script=examples/Nested_function}}
Fōrmulæ programs are not textual, visualization/edition of programs is done showing/manipulating structures but not text. Moreover, there can be multiple visual representations of the same program. Even though it is possible to have textual representation &mdash;i.e. XML, JSON&mdash; they are intended for storage and transfer purposes more than visualization and edition.


'''Solution'''
Programs in Fōrmulæ are created/edited online in its [https://formulae.org website], However they run on execution servers. By default remote servers are used, but they are limited in memory and processing power, since they are intended for demonstration and casual use. A local server can be downloaded and installed, it has no limitations (it runs in your own computer). Because of that, example programs can be fully visualized and edited, but some of them will not run if they require a moderate or heavy computation/memory resources, and no local server is being used.


[[File:Fōrmulæ - Nested function 01.png]]
In '''[https://formulae.org/?example=Nested_function this]''' page you can see the program(s) related to this task and their results.

[[File:Fōrmulæ - Nested function 02.png]]

[[File:Fōrmulæ - Nested function 03.png]]


=={{header|Go}}==
=={{header|Go}}==


<lang go>package main
<syntaxhighlight lang="go">package main
import "fmt"
import "fmt"


Line 697: Line 828:
func main() {
func main() {
fmt.Print(makeList(". "))
fmt.Print(makeList(". "))
}</lang>
}</syntaxhighlight>


=={{header|Haskell}}==
=={{header|Haskell}}==


<lang haskell>import Control.Monad.ST
<syntaxhighlight lang="haskell">import Control.Monad.ST
import Data.STRef
import Data.STRef


Line 716: Line 847:


main :: IO ()
main :: IO ()
main = putStr $ makeList ". "</lang>
main = putStr $ makeList ". "</syntaxhighlight>


Or, importing a little less heavy machinery:
<syntaxhighlight lang="haskell">makeList :: String -> String
makeList separator =
let makeItem = (<>) . (<> separator) . show
in unlines $ zipWith makeItem [1 ..] ["First", "Second", "Third"]

main :: IO ()
main = putStrLn $ makeList ". "</syntaxhighlight>

or perhaps:
<syntaxhighlight lang="haskell">makeList :: String -> String
makeList separator =
let makeItem = unlines . zipWith ((<>) . (<> separator) . show) [1..]
in makeItem ["First", "Second", "Third"]

main :: IO ()
main = putStrLn $ makeList ". "</syntaxhighlight>
{{Out}}
<pre>1. First
2. Second
3. Third</pre>


=={{header|Io}}==
=={{header|Io}}==
<lang Io>makeList := method(separator,
<syntaxhighlight lang="io">makeList := method(separator,
counter := 1
counter := 1
makeItem := method(item,
makeItem := method(item,
Line 728: Line 882:
makeItem("first") .. makeItem("second") .. makeItem("third")
makeItem("first") .. makeItem("second") .. makeItem("third")
)
)
makeList(". ") print</lang>
makeList(". ") print</syntaxhighlight>


=={{header|J}}==
=={{header|J}}==
Line 736: Line 890:
That said, emulating a single level of nesting is relatively trivial and does not reflect the complexities necessary for more elaborate (and more difficult to understand) cases:
That said, emulating a single level of nesting is relatively trivial and does not reflect the complexities necessary for more elaborate (and more difficult to understand) cases:


<lang J>MakeList=: dyad define
<syntaxhighlight lang="j">MakeList=: dyad define
sep_MakeList_=: x
sep_MakeList_=: x
cnt_MakeList_=: 0
cnt_MakeList_=: 0
Line 745: Line 899:
cnt_MakeList_=: cnt_MakeList_+1
cnt_MakeList_=: cnt_MakeList_+1
(":cnt_MakeList_),sep_MakeList_,y,LF
(":cnt_MakeList_),sep_MakeList_,y,LF
)</lang>
)</syntaxhighlight>


Example use:
Example use:


<lang J> '. ' MakeList 'first';'second';'third'
<syntaxhighlight lang="j"> '. ' MakeList 'first';'second';'third'
1. first
1. first
2. second
2. second
3. third
3. third
</syntaxhighlight>
</lang>


=={{header|Java}}==
=={{header|Java}}==
Line 760: Line 914:
Since version 8, Java has limited support for nested functions. All variables from the outer function that are accessed by the inner function have to be _effectively final_. This means that the counter cannot be a simple <tt>int</tt> variable; the closest way to emulate it is the <tt>AtomicInteger</tt> class.
Since version 8, Java has limited support for nested functions. All variables from the outer function that are accessed by the inner function have to be _effectively final_. This means that the counter cannot be a simple <tt>int</tt> variable; the closest way to emulate it is the <tt>AtomicInteger</tt> class.


<lang java>import java.util.concurrent.atomic.AtomicInteger;
<syntaxhighlight lang="java">import java.util.concurrent.atomic.AtomicInteger;
import java.util.function.Function;
import java.util.function.Function;


Line 776: Line 930:
System.out.println(makeList(". "));
System.out.println(makeList(". "));
}
}
}</lang>
}</syntaxhighlight>


=={{header|JavaScript}}==
=={{header|JavaScript}}==


<lang javascript>function makeList(separator) {
<syntaxhighlight lang="javascript">function makeList(separator) {
var counter = 1;
var counter = 1;


Line 790: Line 944:
}
}


console.log(makeList(". "));</lang>
console.log(makeList(". "));</syntaxhighlight>


=={{header|jq}}==
=={{header|jq}}==


<lang jq>def makeList(separator):
<syntaxhighlight lang="jq">def makeList(separator):
# input: {text: _, counter: _}
# input: {text: _, counter: _}
def makeItem(item):
def makeItem(item):
Line 805: Line 959:
;
;
makeList(". ")</lang>
makeList(". ")</syntaxhighlight>


With the above in a file, say program.jq, the invocation:
With the above in a file, say program.jq, the invocation:
Line 818: Line 972:
=={{header|Jsish}}==
=={{header|Jsish}}==
From Javascript entry.
From Javascript entry.
<lang javascript>/* Nested function, in Jsish */
<syntaxhighlight lang="javascript">/* Nested function, in Jsish */
function makeList(separator) {
function makeList(separator) {
var counter = 1;
var counter = 1;
Line 838: Line 992:


=!EXPECTEND!=
=!EXPECTEND!=
*/</lang>
*/</syntaxhighlight>


{{out}}
{{out}}
Line 847: Line 1,001:
{{works with|Julia|0.6}}
{{works with|Julia|0.6}}


<lang julia>function makelist(sep::String)
<syntaxhighlight lang="julia">function makelist(sep::String)
cnt = 1
cnt = 1


Line 859: Line 1,013:
end
end


print(makelist(". "))</lang>
print(makelist(". "))</syntaxhighlight>


=={{header|Kotlin}}==
=={{header|Kotlin}}==
<lang scala>// version 1.0.6
<syntaxhighlight lang="scala">// version 1.0.6


fun makeList(sep: String): String {
fun makeList(sep: String): String {
Line 875: Line 1,029:
fun main(args: Array<String>) {
fun main(args: Array<String>) {
print(makeList(". "))
print(makeList(". "))
}</lang>
}</syntaxhighlight>


{{out}}
{{out}}
Line 883: Line 1,037:
3. third
3. third
</pre>
</pre>

=={{header|Lambdatalk}}==
Lambdatalk has neither closures nor states but we can do that, thanks to mutability of arrays behaving as "sandbox" of mutability.
<syntaxhighlight lang="scheme">
{def makeList

{def makeItem
{lambda {:s :a :i}
{div}{A.first {A.set! 0 {+ {A.first :a} 1} :a}}:s :i}}

{lambda {:s}
{S.map {{lambda {:s :a :i} {makeItem :s :a :i}}
:s {A.new 0}}
first second third
}}}
-> makeList

{makeList .}
->
1. first
2. second
3. third
</syntaxhighlight>


=={{header|Lua}}==
=={{header|Lua}}==


<lang lua>function makeList (separator)
<syntaxhighlight lang="lua">function makeList (separator)
local counter = 0
local counter = 0
local function makeItem(item)
local function makeItem(item)
Line 895: Line 1,072:
end
end
print(makeList(". "))</lang>
print(makeList(". "))</syntaxhighlight>
{{out}}
{{out}}
<pre>1. first
<pre>1. first
Line 904: Line 1,081:
In M2000 functions may have functions, modules, subs, but these are black boxes. We can define globals for temporary use. Subs can use anything from module/function where we call them. First example use Subs inside a module, when call Make_list two local variables, Separator$ and Counter allocated in same space as module's. So when we call Make_item() these variables are visible. At the exit of sub Make_list local variables destroyed. In second example Letter$ pop a string from stack of values (or an error raised if no string found).
In M2000 functions may have functions, modules, subs, but these are black boxes. We can define globals for temporary use. Subs can use anything from module/function where we call them. First example use Subs inside a module, when call Make_list two local variables, Separator$ and Counter allocated in same space as module's. So when we call Make_item() these variables are visible. At the exit of sub Make_list local variables destroyed. In second example Letter$ pop a string from stack of values (or an error raised if no string found).


<syntaxhighlight lang="m2000 interpreter">
<lang M2000 Interpreter>
Module Checkit {
Module Checkit {
Make_List(". ")
Make_List(". ")
Line 946: Line 1,123:


Make_List1 ". "
Make_List1 ". "

</lang>
Module Make_List (Separator$) {
Def Counter as Integer
// Need New before Item_Name$, because the scope is the module scope
// the scope defined from the calling method.
// by default a function has a new namespace.
Function Make_Item(New Item_Name$){
Counter++
Print Str$(Counter,"")+Separator$+Item_Name$
}
// Call Local place the module scope to function
// function called like a module
Call Local Make_Item("First")
Call Local Make_Item("Second")
Call Local Make_Item("Third")
Print "Counter=";Counter // 3
}

Make_List ". "

Module Make_List (Separator$) {
Def Counter
// using Module not Function.
Module Make_Item(New Item_Name$){
Counter++
Print Str$(Counter,"")+Separator$+Item_Name$
}
Call Local Make_Item,"First"
Call Local Make_Item,"Second"
Call Local Make_Item,"Third"
Print "Counter=";Counter // 3
}

Make_List ". "


</syntaxhighlight>


=={{header|Maple}}==
=={{header|Maple}}==
<syntaxhighlight lang="maple">
<lang Maple>
makelist:=proc()
makelist:=proc()
local makeitem,i;
local makeitem,i;
Line 970: Line 1,183:
end proc;
end proc;


</syntaxhighlight>
</lang>


=={{header|Mathematica}}==
=={{header|Mathematica}}/{{header|Wolfram Language}}==
<lang Mathematica>makeList[sep_String]:=Block[
<syntaxhighlight lang="mathematica">makeList[sep_String]:=Block[
{counter=0, makeItem},
{counter=0, makeItem},
makeItem[item_String]:=ToString[++counter]<>sep<>item;
makeItem[item_String]:=ToString[++counter]<>sep<>item;
makeItem /@ {"first", "second", "third"}
makeItem /@ {"first", "second", "third"}
]
]
Scan[Print, makeList[". "]]</lang>
Scan[Print, makeList[". "]]</syntaxhighlight>


=={{header|min}}==
=={{header|min}}==
{{works with|min|0.19.3}}
{{works with|min|0.19.3}}
Note the <code>@</code> sigil is the key to altering <code>counter</code> in the outer scope.
Note the <code>@</code> sigil is the key to altering <code>counter</code> in the outer scope.
<lang min>(
<syntaxhighlight lang="min">(
:separator
:separator
1 :counter
1 :counter
Line 994: Line 1,207:
) :make-list
) :make-list


". " make-list print</lang>
". " make-list print</syntaxhighlight>


=={{header|MiniScript}}==
=={{header|MiniScript}}==
Subfunctions can directly read variables in the enclosing scope, but to assign to those variables, they must explicitly use the ''outer'' specifier (added in MiniScript version 1.5). This is similar to how global variables are accessed via ''globals''.
Subfunctions can directly read variables in the enclosing scope, but to assign to those variables, they must explicitly use the ''outer'' specifier (added in MiniScript version 1.5). This is similar to how global variables are accessed via ''globals''.
<lang MiniScript>makeList = function(sep)
<syntaxhighlight lang="miniscript">makeList = function(sep)
counter = 0
counter = 0
makeItem = function(item)
makeItem = function(item)
Line 1,007: Line 1,220:
end function
end function
print makeList(". ")</lang>
print makeList(". ")</syntaxhighlight>
Output:
Output:
<pre>["1. first", "2. second", "3. third"]</pre>
<pre>["1. first", "2. second", "3. third"]</pre>
Line 1,013: Line 1,226:
=={{header|Nanoquery}}==
=={{header|Nanoquery}}==
{{trans|Python}}
{{trans|Python}}
<lang Nanoquery>def makeList(separator)
<syntaxhighlight lang="nanoquery">def makeList(separator)
counter = 1
counter = 1
Line 1,025: Line 1,238:
end
end


println makeList(". ")</lang>
println makeList(". ")</syntaxhighlight>


=={{header|Nim}}==
=={{header|Nim}}==
<lang nim>proc makeList(separator: string): string =
<syntaxhighlight lang="nim">proc makeList(separator: string): string =
var counter = 1
var counter = 1
Line 1,037: Line 1,250:
makeItem("first") & makeItem("second") & makeItem("third")
makeItem("first") & makeItem("second") & makeItem("third")


echo $makeList(". ")</lang>
echo $makeList(". ")</syntaxhighlight>
{{out}}
{{out}}
<pre>
<pre>
Line 1,047: Line 1,260:
=={{header|Objective-C}}==
=={{header|Objective-C}}==


<lang objc>NSString *makeList(NSString *separator) {
<syntaxhighlight lang="objc">NSString *makeList(NSString *separator) {
__block int counter = 1;
__block int counter = 1;
Line 1,060: Line 1,273:
NSLog(@"%@", makeList(@". "));
NSLog(@"%@", makeList(@". "));
return 0;
return 0;
}</lang>
}</syntaxhighlight>


=={{header|OCaml}}==
=={{header|OCaml}}==


<lang ocaml>let make_list separator =
<syntaxhighlight lang="ocaml">let make_list separator =
let counter = ref 1 in
let counter = ref 1 in


Line 1,076: Line 1,289:


let () =
let () =
print_string (make_list ". ")</lang>
print_string (make_list ". ")</syntaxhighlight>
Interestingly, on my computer it prints the numbers in reverse order, probably because the order of evaluation of arguments (and thus order of access of the counter) is undetermined:
Interestingly, on my computer it prints the numbers in reverse order, probably because the order of evaluation of arguments (and thus order of access of the counter) is undetermined:
{{out}}
{{out}}
Line 1,090: Line 1,303:
=={{header|Perl}}==
=={{header|Perl}}==


<lang perl>sub makeList {
<syntaxhighlight lang="perl">sub makeList {
my $separator = shift;
my $separator = shift;
my $counter = 1;
my $counter = 1;
Line 1,099: Line 1,312:
}
}


print makeList(". ");</lang>
print makeList(". ");</syntaxhighlight>


=={{header|Phix}}==
=={{header|Phix}}==
Line 1,111: Line 1,324:
in 1.0.0 and later, prior to that it simply won't work as hoped for.
in 1.0.0 and later, prior to that it simply won't work as hoped for.
=== using a dictionary ===
=== using a dictionary ===
<lang Phix>function MakeList(string sep=". ")
<syntaxhighlight lang="phix">function MakeList(string sep=". ")
function MakeItem(integer env, string sep)
function MakeItem(integer env, string sep)
integer counter = getd("counter",env)+1
integer counter = getd("counter",env)+1
Line 1,125: Line 1,338:
end function
end function
?MakeList()</lang>
?MakeList()</syntaxhighlight>
{{out}}
{{out}}
<pre>
<pre>
Line 1,133: Line 1,346:
{{libheader|Phix/Class}}
{{libheader|Phix/Class}}
Same output. I trust it is obvious that if you passed in c.count, you would not be able to update it.
Same output. I trust it is obvious that if you passed in c.count, you would not be able to update it.
Again note how MakeList's sep ''must'' be explicitly re-passed to MakeItem.<br>
<lang Phix>class counter
Also note that the counter class ''cannot'' be made private to MakeList, however as a non-global it would automatically be private to a single source code file.
<syntaxhighlight lang="phix">class counter
public integer count
public integer count
end class
end class
Line 1,149: Line 1,364:
end function
end function
?MakeList()</lang>
?MakeList()</syntaxhighlight>


=={{header|PHP}}==
=={{header|PHP}}==
{{works with|PHP|5.3+}}
{{works with|PHP|5.3+}}
<lang php><?
<syntaxhighlight lang="php"><?
function makeList($separator) {
function makeList($separator) {
$counter = 1;
$counter = 1;
Line 1,165: Line 1,380:


echo makeList(". ");
echo makeList(". ");
?></lang>
?></syntaxhighlight>


=={{header|PicoLisp}}==
=={{header|PicoLisp}}==
<lang PicoLisp>(de makeList (Sep)
<syntaxhighlight lang="picolisp">(de makeList (Sep)
(let (Cnt 0 makeItem '((Str) (prinl (inc 'Cnt) Sep Str)))
(let (Cnt 0 makeItem '((Str) (prinl (inc 'Cnt) Sep Str)))
(makeItem "first")
(makeItem "first")
Line 1,174: Line 1,389:
(makeItem "third") ) )
(makeItem "third") ) )


(makeList ". ")</lang>
(makeList ". ")</syntaxhighlight>


=={{header|Python}}==
=={{header|Python}}==
{{works with|Python|3+}}
{{works with|Python|3+}}
<lang python>def makeList(separator):
<syntaxhighlight lang="python">def makeList(separator):
counter = 1
counter = 1


Line 1,189: Line 1,404:
return makeItem("first") + makeItem("second") + makeItem("third")
return makeItem("first") + makeItem("second") + makeItem("third")


print(makeList(". "))</lang>
print(makeList(". "))</syntaxhighlight>
=={{header|R}}==
=={{header|R}}==
This also shows that cat's sep argument is not the same as MakeList's.
This also shows that cat's sep argument is not the same as MakeList's.
<lang r>MakeList <- function(sep)
<syntaxhighlight lang="rsplus">MakeList <- function(sep)
{
{
counter <- 0
counter <- 0
Line 1,198: Line 1,413:
cat(replicate(3, MakeItem()), sep = "\n")
cat(replicate(3, MakeItem()), sep = "\n")
}
}
MakeList(". ")</lang>
MakeList(". ")</syntaxhighlight>
{{out}}
{{out}}
<pre>1. first
<pre>1. first
2. second
2. second
3. third</pre>
3. third</pre>

=={{header|Racket}}==
=={{header|Racket}}==
See also [[#Scheme]]; this demonstrates <code>map</code> a higher order function and <code>begin0</code> a form which saves us having to explicitly remember the result.
See also [[#Scheme]]; this demonstrates <code>map</code> a higher order function and <code>begin0</code> a form which saves us having to explicitly remember the result.


<lang racket>#lang racket
<syntaxhighlight lang="racket">#lang racket


(define (make-list separator)
(define (make-list separator)
Line 1,218: Line 1,434:
(apply string-append (map make-item '(first second third))))
(apply string-append (map make-item '(first second third))))
(display (make-list ". "))</lang>
(display (make-list ". "))</syntaxhighlight>


{{out}}
{{out}}
Line 1,228: Line 1,444:
(formerly Perl 6)
(formerly Perl 6)


<lang perl6>sub make-List ($separator = ') '){
<syntaxhighlight lang="raku" line>sub make-List ($separator = ') '){
my $count = 1;
my $count = 1;


Line 1,236: Line 1,452:
}
}


put make-List('. ');</lang>
put make-List('. ');</syntaxhighlight>
{{out}}
{{out}}
<pre>1. first
<pre>1. first
Line 1,245: Line 1,461:
This REXX version is modeled after the '''FreeBASIC''' example &nbsp; (and it has the
This REXX version is modeled after the '''FreeBASIC''' example &nbsp; (and it has the
same limitations).
same limitations).
<lang rexx>/*REXX program demonstrates that functions can be nested (an outer and inner function).*/
<syntaxhighlight lang="rexx">/*REXX program demonstrates that functions can be nested (an outer and inner function).*/
ctr= 0 /*initialize the CTR REXX variable.*/
ctr= 0 /*initialize the CTR REXX variable.*/
call MakeList '. ' /*invoke MakeList with the separator.*/
call MakeList '. ' /*invoke MakeList with the separator.*/
Line 1,258: Line 1,474:
call MakeItem sep, $ /*invoke the MakeItem function. */
call MakeItem sep, $ /*invoke the MakeItem function. */
end /*while*/
end /*while*/
return</lang>
return</syntaxhighlight>
{{out|output|text=&nbsp; when using the default input:}}
{{out|output|text=&nbsp; when using the default input:}}
<pre>
<pre>
Line 1,267: Line 1,483:


=={{header|Ring}}==
=={{header|Ring}}==
<lang ring>
<syntaxhighlight lang="ring">
# Project : Nested function
# Project : Nested function


Line 1,281: Line 1,497:
makeitem(sep, counter, a[counter])
makeitem(sep, counter, a[counter])
end
end
</syntaxhighlight>
</lang>
Output:
Output:
<pre>
<pre>
Line 1,288: Line 1,504:
3. third
3. third
</pre>
</pre>

=={{header|RPL}}==
===Fully compliant===
The outer function creates the inner function, then deletes it at its last execution step.
The <code>\n</code> substring must be replaced by a <code>Newline</code> character when typing the code.
≪ + OVER →STR SWAP + ROT SWAP + SWAP 1 + ≫ ''''MakeItem'''' STO
"" 1
3 PICK "first\n" '''MakeItem''' 3 PICK "second\n" '''MakeItem''' 3 PICK "third\n" '''MakeItem'''
DROP SWAP DROP
''''MakeItem'''' PURGE
‘'''MakeList'''’ STO

". " '''MakeList'''
{{out}}
<pre>
1: "1. first
2. second
3. third"
</pre>
===Unnamed nested functions===
It is more idiomatic in RPL to use unnamed nested functions, which allows the use of local variables and then increases code readability.
≪ "" 1
1 3 '''FOR''' j
3 PICK { "first\n" "second\n" "third\n" } j GET
→ sep item ≪ DUP →STR sep + item + ROT SWAP + SWAP 1 + ≫
'''NEXT'''
DROP SWAP DROP


=={{header|Ruby}}==
=={{header|Ruby}}==


<lang ruby>def makeList(separator)
<syntaxhighlight lang="ruby">def makeList(separator)
counter = 1
counter = 1


Line 1,303: Line 1,549:
end
end


print makeList(". ")</lang>
print makeList(". ")</syntaxhighlight>


=={{header|Rust}}==
=={{header|Rust}}==
<lang Rust>fn make_list(sep: &str) -> String {
<syntaxhighlight lang="rust">fn make_list(sep: &str) -> String {
let mut counter = 0;
let mut counter = 0;
let mut make_item = |label| {
let mut make_item = |label| {
Line 1,322: Line 1,568:
fn main() {
fn main() {
println!("{}", make_list(". "))
println!("{}", make_list(". "))
}</lang>
}</syntaxhighlight>


{{out}}
{{out}}
Line 1,332: Line 1,578:


=={{header|Scala}}==
=={{header|Scala}}==
<syntaxhighlight lang="scala">
<lang Scala>
def main(args: Array[String]) {
def main(args: Array[String]) {
val sep: String=". "
val sep: String=". "
Line 1,344: Line 1,590:
go("third")
go("third")
}
}
</lang>
</syntaxhighlight>


{{out}}
{{out}}
Line 1,355: Line 1,601:
=={{header|Scheme}}==
=={{header|Scheme}}==


<lang scheme>(define (make-list separator)
<syntaxhighlight lang="scheme">(define (make-list separator)
(define counter 1)
(define counter 1)
Line 1,365: Line 1,611:
(string-append (make-item "first") (make-item "second") (make-item "third")))
(string-append (make-item "first") (make-item "second") (make-item "third")))


(display (make-list ". "))</lang>
(display (make-list ". "))</syntaxhighlight>


=={{header|Seed7}}==
=={{header|Seed7}}==
<lang seed7>$ include "seed7_05.s7i";
<syntaxhighlight lang="seed7">$ include "seed7_05.s7i";


const func string: makeList (in string: separator) is func
const func string: makeList (in string: separator) is func
Line 1,391: Line 1,637:
begin
begin
write(makeList(". "));
write(makeList(". "));
end func;</lang>
end func;</syntaxhighlight>


{{out}}
{{out}}
Line 1,401: Line 1,647:


=={{header|Sidef}}==
=={{header|Sidef}}==
<lang ruby>func make_list(separator = ') ') {
<syntaxhighlight lang="ruby">func make_list(separator = ') ') {


var count = 1
var count = 1
Line 1,411: Line 1,657:
}
}


say make_list('. ')</lang>
say make_list('. ')</syntaxhighlight>
{{out}}
{{out}}
<pre>
<pre>
Line 1,420: Line 1,666:


=={{header|Simula}}==
=={{header|Simula}}==
<lang simula>COMMENT CLASS SIMSET IS SIMULA'S STANDARD LINKED LIST DATA TYPE
<syntaxhighlight lang="simula">COMMENT CLASS SIMSET IS SIMULA'S STANDARD LINKED LIST DATA TYPE
CLASS HEAD IS THE LIST ITSELF
CLASS HEAD IS THE LIST ITSELF
CLASS LINK IS THE ELEMENT OF A LIST
CLASS LINK IS THE ELEMENT OF A LIST
Line 1,477: Line 1,723:


END.
END.
</syntaxhighlight>
</lang>
{{out}}
{{out}}
<pre>
<pre>
Line 1,487: Line 1,733:
=={{header|Standard ML}}==
=={{header|Standard ML}}==


<lang sml>fun make_list separator =
<syntaxhighlight lang="sml">fun make_list separator =
let
let
val counter = ref 1;
val counter = ref 1;
Line 1,501: Line 1,747:
end;
end;


print (make_list ". ")</lang>
print (make_list ". ")</syntaxhighlight>


=={{header|SuperCollider}}==
=={{header|SuperCollider}}==
<syntaxhighlight lang="supercollider">(
<lang SuperCollider>(
f = { |separator|
f = { |separator|
var count = 0;
var count = 0;
Line 1,516: Line 1,762:


f.(".")
f.(".")
</syntaxhighlight>
</lang>


=={{header|Swift}}==
=={{header|Swift}}==


<lang swift>func makeList(_ separator: String) -> String {
<syntaxhighlight lang="swift">func makeList(_ separator: String) -> String {
var counter = 1
var counter = 1
Line 1,532: Line 1,778:
}
}


print(makeList(". "))</lang>
print(makeList(". "))</syntaxhighlight>


=={{header|Tcl}}==
=={{header|Tcl}}==
The code below satisfies the specification (inspired by the Swift example). The inner function MakeItem (which gains read/write access to its caller's variables via upvar) is defined, called, and then discarded by renaming to {}. suchenwi
The code below satisfies the specification (inspired by the Swift example). The inner function MakeItem (which gains read/write access to its caller's variables via upvar) is defined, called, and then discarded by renaming to {}. suchenwi
<lang Tcl>#!/usr/bin/env tclsh
<syntaxhighlight lang="tcl">#!/usr/bin/env tclsh


proc MakeList separator {
proc MakeList separator {
Line 1,551: Line 1,797:
}
}
puts [MakeList ". "]
puts [MakeList ". "]
</syntaxhighlight>
</lang>


=={{header|VBA}}==
=={{header|VBA}}==
<lang vb>Option Explicit
<syntaxhighlight lang="vb">Option Explicit


Private Const Sep As String = ". "
Private Const Sep As String = ". "
Line 1,573: Line 1,819:
Counter = Counter + 1
Counter = Counter + 1
MakeItem = Counter & Sep & Item & vbCrLf
MakeItem = Counter & Sep & Item & vbCrLf
End Function</lang>
End Function</syntaxhighlight>


{{out}}
{{out}}
Line 1,583: Line 1,829:


=={{header|Wren}}==
=={{header|Wren}}==
<lang ecmascript>var makeList = Fn.new { |sep|
<syntaxhighlight lang="wren">var makeList = Fn.new { |sep|
var counter = 0
var counter = 0
var makeItem = Fn.new { |name|
var makeItem = Fn.new { |name|
Line 1,596: Line 1,842:
}
}


makeList.call(". ")</lang>
makeList.call(". ")</syntaxhighlight>


{{out}}
{{out}}
Line 1,606: Line 1,852:


=={{header|XPL0}}==
=={{header|XPL0}}==
<lang XPL0>proc MakeList(Separator);
<syntaxhighlight lang="xpl0">proc MakeList(Separator);
char Separator;
char Separator;
int Counter;
int Counter;
Line 1,621: Line 1,867:
for Counter:= 1 to 3 do MakeItem; \MakeList procedure
for Counter:= 1 to 3 do MakeItem; \MakeList procedure


MakeList(". ") \main procedure</lang>
MakeList(". ") \main procedure</syntaxhighlight>


{{out}}
{{out}}
Line 1,632: Line 1,878:
=={{header|zkl}}==
=={{header|zkl}}==
zkl functions don't have direct access to another functions scope, they are not nested. If a function is defined in another function, the compiler moves it out and hands you a reference to the function. So, you are unable to modify variables in the enclosing scope unless you are given a container which can be modified. Partial application can be used to bind [copies] of scope information to a function, that information is fixed at the point of application and becomes strictly local to the binding function (ie changes do not propagate). A Ref[erence] is a container that holds an object so it can be modified by other entities.
zkl functions don't have direct access to another functions scope, they are not nested. If a function is defined in another function, the compiler moves it out and hands you a reference to the function. So, you are unable to modify variables in the enclosing scope unless you are given a container which can be modified. Partial application can be used to bind [copies] of scope information to a function, that information is fixed at the point of application and becomes strictly local to the binding function (ie changes do not propagate). A Ref[erence] is a container that holds an object so it can be modified by other entities.
<lang zkl>fcn makeList(separator){
<syntaxhighlight lang="zkl">fcn makeList(separator){
counter:=Ref(1); // a container holding a one. A reference.
counter:=Ref(1); // a container holding a one. A reference.
// 'wrap is partial application, in this case binding counter and separator
// 'wrap is partial application, in this case binding counter and separator
Line 1,639: Line 1,885:
}
}
print(makeList(". "));</lang>
print(makeList(". "));</syntaxhighlight>
{{out}}
{{out}}
<pre>
<pre>

Latest revision as of 10:18, 6 January 2024

Task
Nested function
You are encouraged to solve this task according to the task description, using any language you may know.

In many languages, functions can be nested, resulting in outer functions and inner functions. The inner function can access variables from the outer function. In most languages, the inner function can also modify variables in the outer function.


Task

Write a program consisting of two nested functions that prints the following text.

1. first
2. second
3. third

The outer function (called MakeList or equivalent) is responsible for creating the list as a whole and is given the separator ". " as argument. It also defines a counter variable to keep track of the item number. This demonstrates how the inner function can influence the variables in the outer function.

The inner function (called MakeItem or equivalent) is responsible for creating a list item. It accesses the separator from the outer function and modifies the counter.


References



11l

Translation of: Python
F makeList(separator)
   V counter = 1

   F makeItem(item)
      -V result = @counter‘’@separator‘’item"\n"
      @counter++
      R result

   R makeItem(‘first’)‘’makeItem(‘second’)‘’makeItem(‘third’)

print(makeList(‘. ’))
Output:
1. first
2. second
3. third

Ada

with Ada.Text_IO;

procedure Nested_Functions is -- 'Nested_Functions' is the name of 'main' 
   
   type List is array(Natural range <>) of String(1 .. 10);
   
   function Make_List(Separator: String) return List is
      Counter: Natural := 0;
      
      function Make_Item(Item_Name: String) return String is
      begin
	 Counter := Counter + 1; -- local in Make_List, global in Make_Item
	 return(Natural'Image(Counter) & Separator & Item_Name);
      end Make_Item;
      
   begin
      return (Make_Item("First "), Make_Item("Second"), Make_Item("Third "));
   end Make_List;
   
begin -- iterate through the result of Make_List
   for Item of Make_List(". ") loop
      Ada.Text_IO.Put_Line(Item);
   end loop;
end Nested_Functions;
Output:
$ ./nested_functions 
 1. First 
 2. Second
 3. Third 

68000 Assembly

;program starts here, after loading palettes etc.
MOVE.W #3,D1
MOVE.W #'.',D4

JSR MakeList

jmp *              ;halt



MakeList:
	MOVE.W #1,D0
loop_MakeList:
	MOVE.W D0,-(SP)
	        JSR PrintHex
		MOVE.B D4,D0             ;load separator into D0
		JSR PrintChar
		MOVE.B #' ',D0
		JSR PrintChar
	MOVE.W (SP)+,D0
	JSR MakeItem
	CMP.W D0,D1
	BCC loop_MakeList		 ;back to start
	RTS
	
MakeItem:
	MOVE.W D0,D2
	SUBQ.W #1,D2
	LSL.W #2,D2
	LEA PointerToText,A0
	MOVE.L (A0,D2),A3
	JSR PrintString
	JSR NewLine
	ADDQ.W #1,D0
	RTS


	
PointerToText:
	DC.L FIRST,SECOND,THIRD
	
FIRST:
	DC.B "FIRST",0
	EVEN
SECOND:
	DC.B "SECOND",0
	EVEN
THIRD:
	DC.B "THIRD",0
	EVEN
Output:

Output running on MAME

Also displayed here:

01. FIRST
02. SECOND
03. THIRD

ALGOL 68

PROC make list = ( STRING separator )STRING:
     BEGIN
        INT counter := 0;
        PROC make item = ( STRING item )STRING:
             BEGIN
                counter +:= 1;
                whole( counter, 0 ) + separator + item + REPR 10
             END; # make item #
        make item( "first" ) + make item( "second" ) + make item( "third" )
     END; # make list #

print( ( make list( ". " ) ) )

ALGOL W

Algol W strings are fixed length which makes this slightly more complicated than the Algol 68 solution.

begin
    string(30) procedure makeList ( string(2) value separator ) ;
        begin
            string(30) listValue;
            integer counter;
            string(10) procedure makeItem ( string(6) value item
                                          ; integer   value length
                                          ) ;
                begin
                    string(10) listItem;
                    counter := counter + 1;
                    listItem( 0 // 1 ) := code( decode( "0" ) + counter );
                    listItem( 1 // 2 ) := separator;
                    listItem( 3 // 6 ) := item;
                    listItem( 3 + length // 1 ) := code( 10 );
                    listItem
                end; % makeItem %
                counter   := 0;
                listValue := makeItem( "first", 5 );
                listValue(  9 // 10 ) := makeItem( "second", 6 );
                listValue( 19 // 10 ) := makeItem( "third",  5 );
                listValue
         end; % makeList %
    write( makeList( ". " ) )
end.

AppleScript

--------------------- NESTED FUNCTION --------------------

-- makeList :: String -> String
on makeList(separator)
    set counter to 0
    
    -- makeItem :: String -> String
    script makeItem
        on |λ|(x)
            set counter to counter + 1
            
            (counter & separator & x & linefeed) as string
        end |λ|
    end script
    
    map(makeItem, ["first", "second", "third"]) as string
end makeList

--------------------------- TEST -------------------------
on run
    
    makeList(". ")
    
end run


-------------------- GENERIC FUNCTIONS -------------------

-- mReturn :: First-class m => (a -> b) -> m (a -> b)
on mReturn(f)
    -- 2nd class handler function lifted into 1st class script wrapper. 
    if script is class of f then
        f
    else
        script
            property |λ| : f
        end script
    end if
end mReturn


-- map :: (a -> b) -> [a] -> [b]
on map(f, xs)
    -- The list obtained by applying f
    -- to each element of xs.
    tell mReturn(f)
        set lng to length of xs
        set lst to {}
        repeat with i from 1 to lng
            set end of lst to |λ|(item i of xs, i, xs)
        end repeat
        return lst
    end tell
end map
Output:
1. first
2. second
3. third

Note, however, that mutation creates redundant complexity and loss of referential transparency. Functions which modify values outside their own scope are rarely, if ever, necessary, and always best avoided. Simpler and sounder here to derive the incrementing index either by zipping the input list with a range of integers, or by inheriting it from the higher order map function:

-- makeList :: String -> String
on makeList(separator)
    
    -- makeItem :: String -> Int -> String
    script makeItem
        on |λ|(x, i)
            (i & separator & x & linefeed) as string
        end |λ|
    end script
    
    map(makeItem, ["first", "second", "third"]) as string
end makeList

Arturo

makeList: function [separator][
    counter: 1

    makeItem: function [item] .export:[counter][
        result: ~"|counter||separator||item|"
        counter: counter+1
        return result
    ]

    @[
        makeItem "first"
        makeItem "second"
        makeItem "third"
    ]
]

print join.with:"\n" makeList ". "
Output:
1. first
2. second
3. third

ATS

(* ****** ****** *)
//
#include
"share/atspre_staload.hats"
//
(* ****** ****** *)

fun
MakeList
(
  sep: string
) : void = let
//
var count: int = 0
//
val count =
  $UNSAFE.cast{ref(int)}(addr@count)
//
fun
MakeItem
(
  item: string
) : void = let
  val () = !count := !count+1
in
  println! (!count, sep, item)
end // end of [MakeItem]
//
in
  MakeItem"first"; MakeItem"second"; MakeItem"third"
end // end of [MakeList]

(* ****** ****** *)

implement main0() = { val () = MakeList". " }

(* ****** ****** *)

BQN

MakeList  {
    nl@+10  s𝕩  i0
    MakeItem  {i+1  (•Fmt i)s𝕩}
    (⊣∾nl∾⊢)´MakeItem¨"first""second""third"
}
Output:
   MakeList ". "
"1. first
2. second
3. third"

C

I honestly never thought this task could ever be done in C and then I was surprised, again. It turns out that nested functions although not a C standard are supported by GCC. I have used anonymous functions in Java and frankly, I don't see any practical benefit other than making code even harder to read. Then again, that's one of the strengths of C. For example, I still have no clue how come the sprintf line is working correctly. I expected the first line of the list to be '1. second', but no, C is C is C.

Not sure who "I" is; but the reason you don't understand the code near sprintf is it's wrong and works by accident. Use of the variable a second time while it's being preincremented has no behavior. Joshudson (talk) 21:33, 3 March 2020 (UTC)JH


IMPORTANT This implementation will only work with GCC. Go through the link above for details.

#include<stdlib.h>
#include<stdio.h>

typedef struct{
	char str[30];
}item;

item* makeList(char* separator){
	int counter = 0,i;
	item* list = (item*)malloc(3*sizeof(item));
	
	item makeItem(){
		item holder;
		
		char names[5][10] = {"first","second","third","fourth","fifth"};
		
		sprintf(holder.str,"%d%s%s",++counter,separator,names[counter]);
		
		return holder;
	}
	
	for(i=0;i<3;i++)
		list[i] = makeItem();
	
	return list;
}

int main()
{
	int i;
	item* list = makeList(". ");
	
	for(i=0;i<3;i++)
		printf("\n%s",list[i].str);
	
	return 0;
}

Output:

1. first
2. second
3. third

C#

string MakeList(string separator)
{
    int counter = 1;

    Func<string, string> makeItem = item => counter++ + separator + item + "\n";

    return makeItem("first") + makeItem("second") + makeItem("third");
}

Console.WriteLine(MakeList(". "));

Update
As of C#7, we can nest actual methods inside other methods instead of creating delegate instances. They can even be declared after the return statement.

string MakeList2(string separator)
{
    int counter = 1;

    return MakeItem("first") + MakeItem("second") + MakeItem("third");
    //using string interpolation
    string MakeItem(string item) => $"{counter++}{separator}{item}\n";
}

C++

Works with: C++11
#include <iostream>
#include <string>
#include <vector>
 
std::vector<std::string> makeList(std::string separator) {
  auto counter = 0;
  auto makeItem = [&](std::string item) {
    return std::to_string(++counter) + separator + item;
  };
  return {makeItem("first"), makeItem("second"), makeItem("third")};
}

int main() {
  for (auto item : makeList(". "))
    std::cout << item << "\n";
}

Clojure

(defn make-list [separator]
  (let [x (atom 0)]
    (letfn [(make-item [item] (swap! x inc) (println (format "%s%s%s" @x separator item)))]
      (make-item "first")
      (make-item "second")
      (make-item "third"))))

(make-list ". ")
Output:
1. first
2. second
3. third

Common Lisp

(defun my-make-list (separator)
  (let ((counter 0))
    (flet ((make-item (item)
              (format nil "~a~a~a~%" (incf counter) separator item)))
      (concatenate 'string
                   (make-item "first")
                   (make-item "second")
                   (make-item "third")))))

(format t (my-make-list ". "))

PS: A function named make-list is already defined in Common Lisp, see specification.

Cowgol

include "cowgol.coh";
include "strings.coh";

sub MakeList(sep: [uint8], buf: [uint8]): (out: [uint8]) is
    out := buf; # return begin of buffer for ease of use
    var counter: uint32 := 0;

    # Add item to string
    sub AddStr(str: [uint8]) is
        var length := StrLen(str);
        MemCopy(str, length, buf);
        buf := buf + length;
    end sub;

    sub MakeItem(item: [uint8]) is
        counter := counter + 1;
        buf := UIToA(counter, 10, buf);
        AddStr(sep);
        AddStr(item);
        AddStr("\n");
    end sub;

    MakeItem("first");
    MakeItem("second");
    MakeItem("third");
    [buf] := 0; # terminate string
end sub;

var buffer: uint8[100];

print(MakeList(". ", &buffer as [uint8]));
Output:
1. first
2. second
3. third

D

string makeList(string seperator) {
    int counter = 1;

    string makeItem(string item) {
        import std.conv : to;
        return to!string(counter++) ~ seperator ~ item ~ "\n";
    }

    return makeItem("first") ~ makeItem("second") ~ makeItem("third");
}

void main() {
    import std.stdio : writeln;
    writeln(makeList(". "));
}
Output:
1. first
2. second
3. third

Delphi

See Pascal

Ecstasy

module NestedFunction {
    static String makeList(String separator) {
        Int counter = 1;

        function String(String) makeItem = item -> $"{counter++}{separator}{item}\n";

        return makeItem("first")
             + makeItem("second")
             + makeItem("third");
    }

    void run() {
        @Inject Console console;
        console.print(makeList(". "));
    }
}
Output:
1. first
2. second
3. third

Elena

ELENA 6.x :

import extensions;
 
MakeList(separator)
{
    var counter := 1;
 
    var makeItem := (item){ var retVal := counter.toPrintable() + separator + item + newLineConstant; counter += 1; ^ retVal };
 
    ^ makeItem("first") + makeItem("second") + makeItem("third")
}
 
public program()
{
    console.printLine(MakeList(". "))
}
Output:
1. first
2. second
3. third

Elixir

Elixir data are immutable. Anonymous functions are closures and as such they can access variables that are in scope when the function is defined. Keep in mind a variable assigned inside a function does not affect its surrounding environment:

defmodule Nested do
  def makeList(separator) do
    counter = 1
    
    makeItem = fn {}, item ->
                      {"#{counter}#{separator}#{item}\n", counter+1}
                  {result, counter}, item ->
                      {result <> "#{counter}#{separator}#{item}\n", counter+1}
               end
    
    {} |> makeItem.("first") |> makeItem.("second") |> makeItem.("third") |> elem(0)
  end
end

IO.write Nested.makeList(". ")
Output:
1. first
2. second
3. third

EMal

fun makeList = List by text separator
  int counter = 0
  fun makeItem = text by text item
    return ++counter + separator + item
  end
  return text[makeItem("first"), makeItem("second"), makeItem("third")]
end
for each text item in makeList(". ") do writeLine(item) end
Output:
1. first
2. second
3. third

Factor

Words (named functions) cannot be defined with parsing words (such as : or ::) in the definition of another word. However, quotations (anonymous functions) can be. We can easily mimic the required behavior by binding a quotation to a lexical variable named make-item. The only caveat is that we must explicitly call the quotation in order to execute it.

If we really wanted, we could also define a named word inside make-list at run time, using words such as define in the words vocabulary.

USING: io kernel math math.parser locals qw sequences ;
IN: rosetta-code.nested-functions

:: make-list ( separator -- str )
    1 :> counter!    
    [| item |
        counter number>string separator append item append
        counter 1 + counter!
    ] :> make-item
    qw{ first second third } [ make-item call ] map "\n" join
;
    
". " make-list write

Fortran

Arithmetic statement functions

Fortran allows the user to define functions (and subroutines also) but from first Fortran (1958) on these are compiled as separate items and cannot themselves contain the definition of another function (or subroutine) - except for the special form allowing the definition of what is called an arithmetic statement function, such as follows:

      FUNCTION F(X)
       REAL X
       DIST(U,V,W) = X*SQRT(U**2 + V**2 + W**2)    !The contained function.
        T = EXP(X)
        F = T + DIST(T,SIN(X),ATAN(X) + 7)         !Invoked...
      END

This (deranged) function contains within it the definition of function DIST (which must be achieved in a single arithmetic statement), and which has access to all the variables of its containing function as well as its own parameters. The sequence DIST(U,V,W) = etc. would normally be interpreted as an assignment of a value to an element of an array called DIST, but, no such array has been declared so this must therefore be the definition of an arithmetic statement function. Such functions are defined following any declarations of variables, and precede the normal executable statements such as T = EXP(X). Since they are for arithmetic they cannot be used for character manipulations, and the CHARACTER variable only appeared with F77.

Containerisation

With the advent of F90 comes the CONTAINS statement, whereby within a function (or subroutine) but oddly, at its end (but before its END) appears the key word CONTAINS, after which further functions (and subroutines) may be defined in the established manner. These have access to all the variables defined in the containing routine, though if the contained routine declares a name used in the containing routine then that outside name becomes inaccessible.

Such contained routines are not themselves allowed to contain routines, so that the nesting is limited to two levels - except that arithmetic statement functions are available, so that three levels could be employed. Languages such as Algol, pl/i, Pascal, etc. impose no such constraint.

      SUBROUTINE POOBAH(TEXT,L,SEP)	!I've got a little list!
       CHARACTER*(*) TEXT	!The supplied scratchpad.
       INTEGER L		!Its length.
       CHARACTER*(*) SEP	!The separator to be used.
       INTEGER N		!A counter.
        L = 0			!No text is in place.
        N = 0			!No items added.
        CALL ADDITEM("first")	!Here we go.
        CALL ADDITEM("second")
        CALL ADDITEM("third")
       CONTAINS		!Madly, defined after usage.
        SUBROUTINE ADDITEM(X)	!A contained routine.
         CHARACTER*(*) X	!The text of the item.
          N = N + 1			!Count another item in.
          TEXT(L + 1:L + 1) = CHAR(ICHAR("0") + N)	!Place the single-digit number.
          L = L + 1			!Rather than mess with unknown-length numbers.
          LX = LEN(SEP)			!Now for the separator.
          TEXT(L + 1:L + LX) = SEP	!Placed.
          L = L + LX			!Advance the finger.
          LX = LEN(X)			!Trailing spaces will be included.
          TEXT(L + 1:L + LX) = X	!Placed.
          L = L + LX			!Advance the finger.
          L = L + 1			!Finally,
          TEXT(L:L) = CHAR(10)		!Append an ASCII line feed. Starts a new line.
        END SUBROUTINE ADDITEM	!That was bitty.
      END SUBROUTINE POOBAH	!But only had to be written once.

      PROGRAM POKE
      CHARACTER*666 TEXT	!Surely sufficient.
      INTEGER L
      CALL POOBAH(TEXT,L,". ")
      WRITE (6,"(A)") TEXT(1:L)
      END

Fortran doesn't offer a "list" construction as a built-in facility so it seemed easiest to prepare the list in a CHARACTER variable. These do not have a length attribute as in a string, the LEN function reports the size of the character variable not something such as the current length of a string varying from zero to the storage limit. So, the length of the in-use portion is tracked with the aid of an auxiliary variable, and one must decide on a sufficiently large scratchpad area to hold the anticipated result. And, since the items are of varying length, the length of the whole sequence is returned, not the number of items. Subroutine POOBAH could be instead a function, but, it would have to return a fixed-size result (as in say CHARACTER*66 FUNCTION POOBAH(SEP)) and can't return a length as well, unless via messing with a global variable such as in COMMON or via an additional parameter as with the L above.

To achieve the required output of one item per line would mean the output of one item at a time, and all the items are packed into TEXT with unknown boundaries. A single character sequence seemed less trouble, but to achieve the one-item-per-line layout meant inserting control codes to start a new line. Oddly, the CHAR(10) is the linefeed character in ASCII but on this windows system it is treated as CRLF whereas CR returned to the start of the line with no advance. If output were to go to an old-style lineprinter, such in-line control codes would not be recognised.

Placing all the texts into one "pool" storage area saves space when items are a different length, but items can only be accessed sequentially. If item i were desired, it can only be found after stepping along from the start and if the collection expands beyond a few dozen items, repeated random access soon becomes slow. If this is important, rather than have the items separated by a special in-line symbol one can instead have an array of fingers to say the end of each item's text, which can thereby contain any symbol. In this case the pooled storage for the texts wastes no space on special symbols but this index array must have some predefined size (and be capable of indexing the size of the pool: 8-bits? 16-bits? 32-bits?), so once again, how long is a piece of string?

When storage is abundant

Another way of providing a "list" is via an array as in CHARACTER*28 TEXT(9)) so that each item occupied one element, and the maddening question "how long is a piece of string" arises twice: how much storage to allow for each element when all must be as long as the longest text expected, and, how many elements are to be allowed for.

      SUBROUTINE POOBAH(TEXT,N,SEP)	!I've got a little list!
       CHARACTER*(*) TEXT(*)	!The supplied scratchpad.
       INTEGER N		!Entry count.
       CHARACTER*(*) SEP	!The separator to be used.
        N = 0			!No items added.
        CALL ADDITEM("first")	!Here we go.
        CALL ADDITEM("second")
        CALL ADDITEM("third")
       CONTAINS		!Madly, defined after usage.
        SUBROUTINE ADDITEM(X)	!A contained routine.
         CHARACTER*(*) X	!The text of the item to add.
          N = N + 1			!Count another item in.
          WRITE (TEXT(N),1) N,SEP,X	!Place the N'th text, suitably decorated..
    1     FORMAT (I1,2A)		!Allowing only a single digit.
        END SUBROUTINE ADDITEM	!That was simple.
      END SUBROUTINE POOBAH	!Still worth a subroutine.

      PROGRAM POKE
      CHARACTER*28 TEXT(9)	!Surely sufficient.
      INTEGER N
      CALL POOBAH(TEXT,N,". ")
      WRITE (6,"(A)") (TEXT(I)(1:LEN_TRIM(TEXT(I))), I = 1,N)
      END

The output statement could be WRITE (6,"(A)") TEXT(1:N) but this would write out the trailing spaces in each element. A TRIM intrinsic function may be available, but, leading spaces may be desired in the case that there are to be more than nine elements. If so, FORMAT (I2,2A) would be needed up to ninety-nine, or more generally, I0 format. Except that would not write out leading spaces and would spoil the neatness of a columnar layout. With file names, the lack of leading spaces (or zero digits) leads to the ideas explored in "Natural" sorting. One could define constants via the PARAMETER statement to document the linkage between the number of array elements and the correct FORMAT code, though this is messy because for NMAX elements the format code requires <Log10(NMAX) + 1> digits, and in such an attempt I've seen Log10(10) come out not as one but as 0·9999932 or somesuch, truncating to zero.

F95 introduced facilities whereby a string-style compound variable with both content and current length could be defined and manipulated, and when assigned to it would be reallocated storage so as to have exactly the size to hold the result. Later fortran standardised such a scheme. Similarly, one could define a data aggregate containing a count N as well as the TEXT array and a function could return such a compound entity as its result. It may also be possible to arrange that array TEXT becomes "ragged", that is, TEXT(i) is not always 28 characters long, but only as much as is needed to store the actual item.

Free Pascal

// In Pascal, functions always _have_ to return _some_ value,
// but the the task doesn’t specify what to return.
// Hence makeList and makeItem became procedures.
procedure makeList(const separator: string);
// The var-section for variables that ought to be accessible
// in the routine’s body as well as the /nested/ routines
// has to appear /before/ the nested routines’ definitions.
var
	counter: 1..high(integer);
	
	procedure makeItem;
	begin
		write(counter, separator);
		case counter of
			1:
			begin
				write('first');
			end;
			2:
			begin
				write('second');
			end;
			3:
			begin
				write('third');
			end;
		end;
		writeLn();
		counter := counter + 1;
	end;
// You can insert another var-section here, but variables declared
// in this block would _not_ be accessible in the /nested/ routine.
begin
	counter := 1;
	makeItem;
	makeItem;
	makeItem;
end;

FreeBASIC

FreeBASIC does not currently support either nested procedures or lambda expressions. The best we can do here is to create two separate procedures but pass the state of the first procedure by reference to the second procedure so it can be modified by the latter.

' FB 1.05.0 Win64

Sub makeItem(sep As String, ByRef counter As Integer, text As String)
  counter += 1
  Print counter; sep; text 
End Sub

Sub makeList(sep As String)
  Dim a(0 To 2) As String = {"first", "second", "third"} 
  Dim counter As Integer = 0
  While counter < 3
    makeItem(sep, counter, a(counter))
  Wend
End Sub

makeList ". "
Print
Print "Press any key to quit"
Sleep
Output:
 1. first
 2. second
 3. third

Fōrmulæ

Fōrmulæ programs are not textual, visualization/edition of programs is done showing/manipulating structures but not text. Moreover, there can be multiple visual representations of the same program. Even though it is possible to have textual representation —i.e. XML, JSON— they are intended for storage and transfer purposes more than visualization and edition.

Programs in Fōrmulæ are created/edited online in its website.

In this page you can see and run the program(s) related to this task and their results. You can also change either the programs or the parameters they are called with, for experimentation, but remember that these programs were created with the main purpose of showing a clear solution of the task, and they generally lack any kind of validation.

Solution

Go

package main
import "fmt"

func makeList(separator string) string {
    counter := 1

    makeItem := func(item string) string {
        result := fmt.Sprintf("%d%s%s\n", counter, separator, item)
        counter += 1
        return result
    }

    return makeItem("first") + makeItem("second") + makeItem("third")
}

func main() {
    fmt.Print(makeList(". "))
}

Haskell

import Control.Monad.ST
import Data.STRef

makeList :: String -> String
makeList separator = concat $ runST $ do
  counter <- newSTRef 1
  let makeItem item = do
        x <- readSTRef counter
        let result = show x ++ separator ++ item ++ "\n"
        modifySTRef counter (+ 1)
        return result
  mapM makeItem ["first", "second", "third"]


main :: IO ()
main = putStr $ makeList ". "


Or, importing a little less heavy machinery:

makeList :: String -> String
makeList separator =
  let makeItem = (<>) . (<> separator) . show
   in unlines $ zipWith makeItem [1 ..] ["First", "Second", "Third"]

main :: IO ()
main = putStrLn $ makeList ". "

or perhaps:

makeList :: String -> String
makeList separator =
  let makeItem = unlines . zipWith ((<>) . (<> separator) . show) [1..]
   in makeItem ["First", "Second", "Third"]

main :: IO ()
main = putStrLn $ makeList ". "
Output:
1. First
2. Second
3. Third

Io

makeList := method(separator,
    counter := 1
    makeItem := method(item,
        result := counter .. separator .. item .. "\n"
        counter = counter + 1
        result
    )
    makeItem("first") .. makeItem("second") .. makeItem("third")
)
makeList(". ") print

J

J does not have nested scopes, so they must be emulated. (The design philosophy here is that nesting tends to become difficult to understand when taken too far, so the coder and designer should be mildly penalized with extra work for choosing nesting as opposed to some other problem solving approach.)

That said, emulating a single level of nesting is relatively trivial and does not reflect the complexities necessary for more elaborate (and more difficult to understand) cases:

MakeList=: dyad define
  sep_MakeList_=: x
  cnt_MakeList_=: 0
  ;MakeItem each y
)

MakeItem=: verb define
  cnt_MakeList_=: cnt_MakeList_+1
  (":cnt_MakeList_),sep_MakeList_,y,LF
)

Example use:

   '. ' MakeList 'first';'second';'third'
1. first
2. second
3. third

Java

Works with: Java version 8

Since version 8, Java has limited support for nested functions. All variables from the outer function that are accessed by the inner function have to be _effectively final_. This means that the counter cannot be a simple int variable; the closest way to emulate it is the AtomicInteger class.

import java.util.concurrent.atomic.AtomicInteger;
import java.util.function.Function;

public class NestedFunctionsDemo {

    static String makeList(String separator) {
        AtomicInteger counter = new AtomicInteger(1);

        Function<String, String> makeItem = item -> counter.getAndIncrement() + separator + item + "\n";

        return makeItem.apply("first") + makeItem.apply("second") + makeItem.apply("third");
    }

    public static void main(String[] args) {
        System.out.println(makeList(". "));
    }
}

JavaScript

function makeList(separator) {
  var counter = 1;

  function makeItem(item) {
    return counter++ + separator + item + "\n";
  }

  return makeItem("first") + makeItem("second") + makeItem("third");
}

console.log(makeList(". "));

jq

def makeList(separator):
  # input: {text: _, counter: _}
  def makeItem(item):
     (.counter + 1) as $counter
     | .text += "\($counter)\(separator)\(item)\n"
     | .counter = $counter;

   {text:"", counter:0} | makeItem("first") | makeItem("second") | makeItem("third") 
   | .text
;
 
makeList(". ")

With the above in a file, say program.jq, the invocation:

   $ jq -n -r -f program.jq

produces:

1. first
2. second
3. third

Jsish

From Javascript entry.

/* Nested function, in Jsish */
function makeList(separator) {
  var counter = 1;

  function makeItem(item) {
    return counter++ + separator + item + "\n";
  }

  return makeItem("first") + makeItem("second") + makeItem("third");
}

;makeList('. ');

/*
=!EXPECTSTART!=
makeList('. ') ==> 1. first
2. second
3. third

=!EXPECTEND!=
*/
Output:
prompt$ jsish -u nestedFunction.jsi
[PASS] nestedFunction.jsi

Julia

Works with: Julia version 0.6
function makelist(sep::String)
    cnt = 1

    function makeitem(item::String)
        rst = string(cnt, sep, item, '\n')
        cnt += 1
        return rst
    end

    return makeitem("first") * makeitem("second") * makeitem("third")
end

print(makelist(". "))

Kotlin

// version 1.0.6

fun makeList(sep: String): String {
    var count = 0
    fun makeItem(item: String): String {
        count++
        return "$count$sep$item\n"
    }    
    return makeItem("first") + makeItem("second") + makeItem("third")
}

fun main(args: Array<String>) {
    print(makeList(". "))
}
Output:
1. first
2. second
3. third

Lambdatalk

Lambdatalk has neither closures nor states but we can do that, thanks to mutability of arrays behaving as "sandbox" of mutability.

{def makeList

 {def makeItem
  {lambda {:s :a :i}
   {div}{A.first {A.set! 0 {+ {A.first :a} 1} :a}}:s :i}}

 {lambda {:s}
  {S.map {{lambda {:s :a :i} {makeItem :s :a :i}} 
                   :s {A.new 0}}
         first second third
}}}     
-> makeList 

{makeList .}
-> 
1. first 
2. second 
3. third

Lua

function makeList (separator)
    local counter = 0
    local function makeItem(item)
            counter = counter + 1
            return counter .. separator .. item .. "\n"
        end
    return makeItem("first") .. makeItem("second") .. makeItem("third")
end
 
print(makeList(". "))
Output:
1. first
2. second
3. third

M2000 Interpreter

In M2000 functions may have functions, modules, subs, but these are black boxes. We can define globals for temporary use. Subs can use anything from module/function where we call them. First example use Subs inside a module, when call Make_list two local variables, Separator$ and Counter allocated in same space as module's. So when we call Make_item() these variables are visible. At the exit of sub Make_list local variables destroyed. In second example Letter$ pop a string from stack of values (or an error raised if no string found).

Module Checkit {
      Make_List(". ")
      Sub Make_List(Separator$)
            Local Counter=0
            Make_Item("First")
            Make_Item("Second")
            Make_Item("Third")
      End Sub
      Sub Make_Item(Item_Name$)
            Counter++
            Print Str$(Counter,"")+Separator$+Item_Name$
      End Sub
}
Checkit

Module Make_List  {
      Global Counter=0, Separator$=Letter$
      Make_Item("First")
      Make_Item("Second")
      Make_Item("Third")
      
      Sub Make_Item(Item_Name$)
            Counter++
            Print Str$(Counter,"")+Separator$+Item_Name$
      End Sub
}

Make_List ". "

Module Make_List1  {
      Global Counter=0, Separator$=Letter$
      Module Make_Item (Item_Name$) {
            Counter++
            Print Str$(Counter,"")+Separator$+Item_Name$
      }
      Make_Item "First" 
      Make_Item "Second" 
      Make_Item "Third" 
}

Make_List1 ". "

Module Make_List (Separator$) {
      Def Counter as Integer
      // Need New before Item_Name$, because the scope is the module scope
      // the scope defined from the calling method.
      // by default a function has a new namespace. 
      Function Make_Item(New Item_Name$){
            Counter++
            Print Str$(Counter,"")+Separator$+Item_Name$
      }
      // Call Local place the module scope to function
      // function called like a module
      Call Local Make_Item("First")
      Call Local Make_Item("Second")
      Call Local Make_Item("Third")
      Print "Counter=";Counter  // 3
}

Make_List ". "

Module Make_List (Separator$) {
      Def Counter
      // using Module not Function.
      Module Make_Item(New Item_Name$){
            Counter++
            Print Str$(Counter,"")+Separator$+Item_Name$
      }
      Call Local Make_Item,"First"
      Call Local Make_Item,"Second"
      Call Local Make_Item,"Third"
      Print "Counter=";Counter  // 3
}

Make_List ". "

Maple

makelist:=proc()
	local makeitem,i;
	i:=1;
	makeitem:=proc(i)
		if i=1 then
			printf("%a\n", "1. first");
		elif i=2 then
			printf("%a\n","2. second");
		elif i=3 then
			printf("%a\n", "3. third");
		else
			return NULL;
		end if;
	end proc;
	while i<4 do
		makeitem(i);
		i:=i+1;
	end do;
end proc;

Mathematica/Wolfram Language

makeList[sep_String]:=Block[
  {counter=0, makeItem},
  makeItem[item_String]:=ToString[++counter]<>sep<>item;
  makeItem /@ {"first", "second", "third"}
  ]
Scan[Print, makeList[". "]]

min

Works with: min version 0.19.3

Note the @ sigil is the key to altering counter in the outer scope.

(
  :separator
  1 :counter
  (
    :item
    item separator counter string ' append append "" join
    counter succ @counter
  ) :make-item
  ("first" "second" "third") 'make-item map "\n" join
) :make-list

". " make-list print

MiniScript

Subfunctions can directly read variables in the enclosing scope, but to assign to those variables, they must explicitly use the outer specifier (added in MiniScript version 1.5). This is similar to how global variables are accessed via globals.

makeList = function(sep)
    counter = 0
    makeItem = function(item)
        outer.counter = counter + 1
        return counter + sep + item
    end function
    return [makeItem("first"), makeItem("second"), makeItem("third")]
end function
 
print makeList(". ")

Output:

["1. first", "2. second", "3. third"]

Nanoquery

Translation of: Python
def makeList(separator)
	counter = 1
	
	def makeItem(item)
		result = str(counter) + separator + item + "\n"
		counter += 1
		return result
	end

	return makeItem("first") + makeItem("second") + makeItem("third")
end

println makeList(". ")

Nim

proc makeList(separator: string): string =
  var counter = 1
  
  proc makeItem(item: string): string =
    result = $counter & separator & item & "\n"
    inc counter
  
  makeItem("first") & makeItem("second") & makeItem("third")

echo $makeList(". ")
Output:
1. first
2. second
3. third

Objective-C

NSString *makeList(NSString *separator) {
  __block int counter = 1;
  
  NSString *(^makeItem)(NSString *) = ^(NSString *item) {
    return [NSString stringWithFormat:@"%d%@%@\n", counter++, separator, item];
  };
  
  return [NSString stringWithFormat:@"%@%@%@", makeItem(@"first"), makeItem(@"second"), makeItem(@"third")];
}

int main() {
  NSLog(@"%@", makeList(@". "));
  return 0;
}

OCaml

let make_list separator =
  let counter = ref 1 in

  let make_item item =
    let result = string_of_int !counter ^ separator ^ item ^ "\n" in
    incr counter;
    result
  in

  make_item "first" ^ make_item "second" ^ make_item "third"

let () =
  print_string (make_list ". ")

Interestingly, on my computer it prints the numbers in reverse order, probably because the order of evaluation of arguments (and thus order of access of the counter) is undetermined:

Output:
3. first
2. second
1. third

Pascal

See Free Pascal

Perl

sub makeList {
    my $separator = shift;
    my $counter = 1;

    sub makeItem { $counter++ . $separator . shift . "\n" }

    makeItem("first") . makeItem("second") . makeItem("third")
}

print makeList(". ");

Phix

There is only partial support for nested functions in Phix. Some prior work (over a single afternoon) has been left unfinished, anyone interested can see it at Nested_function/Phix, but it was just enough to open the door for the two following reasonably acceptable work-arounds.
Note that in both the following you cannot reference any local variables or parameters of the containing function, but must pass in everything you need explicitly, and anything you need to update must be a reference type, which is only dictionaries and class instances, not integers, atoms, sequences, strings, or any user-defined types, as they are all effectively read-only. Referring to identifiers in the containing/outer function issues proper errors in 1.0.0 and later, prior to that it simply won't work as hoped for.

using a dictionary

function MakeList(string sep=".  ")
    function MakeItem(integer env, string sep)
        integer counter = getd("counter",env)+1
        setd("counter",counter,env)
        return sprintf("%d%s%s",{counter,sep,{"first","second","third"}[counter]})
    end function
    integer counter = new_dict({{"counter",0}})
    sequence res = {}
    for i=1 to 3 do
        res = append(res,MakeItem(counter,sep))
    end for
    return res
end function
 
?MakeList()
Output:
{"1.  first","2.  second","3.  third"}

using a class

Library: Phix/Class

Same output. I trust it is obvious that if you passed in c.count, you would not be able to update it. Again note how MakeList's sep must be explicitly re-passed to MakeItem.
Also note that the counter class cannot be made private to MakeList, however as a non-global it would automatically be private to a single source code file.

class counter
    public integer count
end class
function MakeList(string sep=".  ")
    function MakeItem(counter c, string sep)
        c.count += 1
        return sprintf("%d%s%s",{c.count,sep,{"first","second","third"}[c.count]})
    end function
    counter c = new()
    sequence res = {}
    for i=1 to 3 do
        res = append(res,MakeItem(c,sep))
    end for
    return res
end function
 
?MakeList()

PHP

Works with: PHP version 5.3+
<?
function makeList($separator) {
  $counter = 1;

  $makeItem = function ($item) use ($separator, &$counter) {
    return $counter++ . $separator . $item . "\n";
  };

  return $makeItem("first") . $makeItem("second") . $makeItem("third");
}

echo makeList(". ");
?>

PicoLisp

(de makeList (Sep)
   (let (Cnt 0  makeItem '((Str) (prinl (inc 'Cnt) Sep Str)))
      (makeItem "first")
      (makeItem "second")
      (makeItem "third") ) )

(makeList ". ")

Python

Works with: Python version 3+
def makeList(separator):
    counter = 1

    def makeItem(item):
        nonlocal counter
        result = str(counter) + separator + item + "\n"
        counter += 1
        return result

    return makeItem("first") + makeItem("second") + makeItem("third")

print(makeList(". "))

R

This also shows that cat's sep argument is not the same as MakeList's.

MakeList <- function(sep)
{
  counter <- 0
  MakeItem <- function() paste0(counter <<- counter + 1, sep, c("first", "second", "third")[counter])
  cat(replicate(3, MakeItem()), sep = "\n")
}
MakeList(". ")
Output:
1. first
2. second
3. third

Racket

See also #Scheme; this demonstrates map a higher order function and begin0 a form which saves us having to explicitly remember the result.

#lang racket

(define (make-list separator)
  (define counter 1)
 
  (define (make-item item)
    (begin0
      (format "~a~a~a~%" counter separator item)
      (set! counter (add1 counter))))
 
  (apply string-append (map make-item '(first second third))))
 
(display (make-list ". "))
Output:
1. first
2. second
3. third

Raku

(formerly Perl 6)

sub make-List ($separator = ') '){
    my $count = 1;

    sub make-Item ($item) { "{$count++}$separator$item" }

    join "\n", <first second third>».&make-Item;
}

put make-List('. ');
Output:
1. first
2. second
3. third

REXX

This REXX version is modeled after the FreeBASIC example   (and it has the same limitations).

/*REXX program demonstrates that functions can be nested  (an outer and inner function).*/
ctr= 0                                           /*initialize the   CTR   REXX variable.*/
call MakeList '. '                               /*invoke  MakeList  with the separator.*/
exit 0                                           /*stick a fork in it,  we're all done. */
/*──────────────────────────────────────────────────────────────────────────────────────*/
MakeItem: parse arg sep,text;    ctr= ctr + 1    /*bump the counter variable.           */
          say ctr  ||  sep  ||  word($, ctr)     /*display three thingys ───► terminal. */
          return
/*──────────────────────────────────────────────────────────────────────────────────────*/
MakeList: parse arg sep; $= 'first second third' /*obtain an argument;  define a string.*/
                     do  while  ctr<3            /*keep truckin'  until  finished.      */
                     call MakeItem  sep, $       /*invoke the   MakeItem   function.    */
                     end   /*while*/
          return
output   when using the default input:
1. first
2. second
3. third

Ring

# Project : Nested function

makeList(". ")
func makeitem(sep, counter, text)
       see "" + counter + sep + text + nl
 
func makelist(sep)
       a = ["first", "second", "third"] 
       counter = 0
       while counter < 3
                counter = counter + 1
                makeitem(sep, counter, a[counter])
       end

Output:

1. first
2. second
3. third

RPL

Fully compliant

The outer function creates the inner function, then deletes it at its last execution step. The \n substring must be replaced by a Newline character when typing the code.

≪ 
   ≪ + OVER →STR SWAP + ROT SWAP + SWAP 1 + ≫ 'MakeItem' STO
   "" 1 
   3 PICK "first\n" MakeItem 3 PICK "second\n" MakeItem 3 PICK "third\n" MakeItem
   DROP SWAP DROP 
   'MakeItem' PURGE
≫
‘MakeList’ STO
". " MakeList
Output:
 1: "1. first
    2. second
    3. third"

Unnamed nested functions

It is more idiomatic in RPL to use unnamed nested functions, which allows the use of local variables and then increases code readability.

≪ "" 1 
   1 3 FOR j 
       3 PICK { "first\n" "second\n" "third\n" } j GET 
       → sep item ≪ DUP →STR sep + item + ROT SWAP + SWAP 1 + ≫
   NEXT
   DROP SWAP DROP 
≫

Ruby

def makeList(separator)
  counter = 1

  makeItem = lambda {|item|
    result = "#{counter}#{separator}#{item}\n"
    counter += 1
    result
  }

  makeItem["first"] + makeItem["second"] + makeItem["third"]
end

print makeList(". ")

Rust

fn make_list(sep: &str) -> String {
    let mut counter = 0;
    let mut make_item = |label| {
        counter += 1;
        format!("{}{}{}", counter, sep, label)
    };
    format!(
        "{}\n{}\n{}",
        make_item("First"),
        make_item("Second"),
        make_item("Third")
    )
}

fn main() {
    println!("{}", make_list(". "))
}
Output:
1. First
2. Second
3. Third

Scala

   def main(args: Array[String]) {
      val sep: String=". "
      var c:Int=1;
      def go(s: String):Unit={
          println(c+sep+s)
          c=c+1
      }
      go("first")
      go("second")
      go("third")
   }
Output:
1. first
2. second
3. third

Scheme

(define (make-list separator)
  (define counter 1)
  
  (define (make-item item)
    (let ((result (string-append (number->string counter) separator item "\n")))
      (set! counter (+ counter 1))
      result))
  
  (string-append (make-item "first") (make-item "second") (make-item "third")))

(display (make-list ". "))

Seed7

$ include "seed7_05.s7i";

const func string: makeList (in string: separator) is func
  result
    var string: itemList is "";
  local
    var integer: counter is 1;

    const func string: makeItem (in string: item) is func
      result
        var string: anItem is "";
      begin
        anItem := counter <& separator <& item <& "\n";
	incr(counter);
      end func

  begin
    itemList := makeItem("first") & makeItem("second") & makeItem("third");
  end func;

const proc: main is func
  begin
    write(makeList(". "));
  end func;
Output:
1. first
2. second
3. third

Sidef

func make_list(separator = ') ') {

    var count = 1
    func make_item(item) {
        [count++, separator, item].join
    }

    <first second third>.map(make_item).join("\n")
}

say make_list('. ')
Output:
1. first
2. second
3. third

Simula

COMMENT CLASS SIMSET IS SIMULA'S STANDARD LINKED LIST DATA TYPE
        CLASS HEAD IS THE LIST ITSELF
        CLASS LINK IS THE ELEMENT OF A LIST
        PROCEDURE IS THE TERM USED FOR FUNCTIONS IN SIMULA
        TEXT IS THE TERM USED FOR STRINGS IN SIMULA ;
SIMSET
BEGIN

    LINK CLASS ITEM(TXT); TEXT TXT;;

    COMMENT CREATING THE LIST AS A WHOLE WITH THE SEPARATOR ". "
            GIVEN AS AN ARGUMENT;
    REF(HEAD) PROCEDURE MAKELIST(SEPARATOR); TEXT SEPARATOR;
    BEGIN
        COMMENT VARIABLE TO KEEP TRACK OF THE ITEM NUMBER ;
        INTEGER COUNTER;

        COMMENT THIS IS THE NESTED FUNCTION ;
        REF(ITEM) PROCEDURE MAKEITEM(TXT); TEXT TXT;
        BEGIN
            TEXT NUM;
            TEXT ITEMTEXT;

            COMMENT CONVERT NUMBER TO STRING ;
            NUM :- BLANKS(5);
            NUM.PUTINT(COUNTER);

            COMMENT ACCESS SEPARATOR AND MODIFY COUNTER;
            COUNTER := COUNTER + 1;
            ITEMTEXT :- NUM & SEPARATOR & TXT;

            MAKEITEM :- NEW ITEM(ITEMTEXT);
        END MAKEITEM;

        REF(HEAD) HD;
        HD :- NEW HEAD;
        COUNTER := 1;
        MAKEITEM("FIRST").INTO(HD);
        MAKEITEM("SECOND").INTO(HD);
        MAKEITEM("THIRD").INTO(HD);
        MAKELIST :- HD;
    END MAKELIST;

    REF(HEAD) LIST;
    REF(ITEM) IT;
    LIST :- MAKELIST(". ");

    COMMENT NAVIGATE THROUGH THE LIST ;
    IT :- LIST.FIRST;
    WHILE IT =/= NONE DO
    BEGIN
        OUTTEXT(IT.TXT);
        OUTIMAGE;
        IT :- IT.SUC;
    END;

END.
Output:
    1. FIRST
    2. SECOND
    3. THIRD

Standard ML

fun make_list separator =
  let
    val counter = ref 1;
    fun make_item item =
      let
        val result = Int.toString (!counter) ^ separator ^ item ^ "\n"
      in
        counter := !counter + 1;
        result
      end
  in
    make_item "first" ^ make_item "second" ^ make_item "third"
  end;

print (make_list ". ")

SuperCollider

(
f = { |separator|
	var count = 0;
	var counting = { |name|
		count = count + 1;
		count.asString ++ separator + name ++ "\n"
	};
	counting.("first") + counting.("second") + counting.("third")
};
)

f.(".")

Swift

func makeList(_ separator: String) -> String {
  var counter = 1
  
  func makeItem(_ item: String) -> String {
    let result = String(counter) + separator + item + "\n"
    counter += 1
    return result
  }
  
  return makeItem("first") + makeItem("second") + makeItem("third")
}

print(makeList(". "))

Tcl

The code below satisfies the specification (inspired by the Swift example). The inner function MakeItem (which gains read/write access to its caller's variables via upvar) is defined, called, and then discarded by renaming to {}. suchenwi

#!/usr/bin/env tclsh

proc MakeList separator {
    set counter 1
    proc MakeItem string {
	upvar 1 separator separator counter counter
	set res $counter$separator$string\n
	incr counter
	return $res
    }
    set res [MakeItem first][MakeItem second][MakeItem third]
    rename MakeItem {}
    return $res
}
puts [MakeList ". "]

VBA

Option Explicit

Private Const Sep As String = ". "
Private Counter As Integer
Sub Main()
Dim L As Variant
    Counter = 0
    L = MakeList(Array("first", "second", "third"))
    Debug.Print L
End Sub
Function MakeList(Datas) As Variant
Dim i As Integer
    For i = LBound(Datas) To UBound(Datas)
        MakeList = MakeList & MakeItem(Datas(i))
    Next i
End Function
Function MakeItem(Item As Variant) As Variant
    Counter = Counter + 1
    MakeItem = Counter & Sep & Item & vbCrLf
End Function
Output:
1. first
2. second
3. third

Wren

var makeList = Fn.new { |sep|
    var counter = 0
    var makeItem = Fn.new { |name|
        counter = counter + 1
        return "%(counter)%(sep)%(name)"
    }
    var items = []
    for (name in ["first", "second", "third"]) {
        items.add(makeItem.call(name))
    }
    System.print(items.join("\n"))
}

makeList.call(". ")
Output:
1. first
2. second
3. third

XPL0

proc    MakeList(Separator);
char    Separator;
int     Counter;

    proc MakeItem;
    int  Ordinals;
    [IntOut(0, Counter);
    Text(0, Separator);
    Ordinals:= [0, "first", "second", "third"];
    Text(0, Ordinals(Counter));
    CrLf(0);
    ];

for Counter:= 1 to 3 do MakeItem;       \MakeList procedure

MakeList(". ")                          \main procedure
Output:
1. first
2. second
3. third

zkl

zkl functions don't have direct access to another functions scope, they are not nested. If a function is defined in another function, the compiler moves it out and hands you a reference to the function. So, you are unable to modify variables in the enclosing scope unless you are given a container which can be modified. Partial application can be used to bind [copies] of scope information to a function, that information is fixed at the point of application and becomes strictly local to the binding function (ie changes do not propagate). A Ref[erence] is a container that holds an object so it can be modified by other entities.

fcn makeList(separator){
  counter:=Ref(1);  // a container holding a one. A reference.
  // 'wrap is partial application, in this case binding counter and separator
  makeItem:='wrap(item){ c:=counter.inc(); String(c,separator,item,"\n") };
  makeItem("first") + makeItem("second") + makeItem("third")
}
 
print(makeList(". "));
Output:
1. first
2. second
3. third