Topic variable: Difference between revisions

m
→‎{{header|Wren}}: Changed to Wren S/H
m (→‎{{header|Wren}}: Changed to Wren S/H)
 
(4 intermediate revisions by 4 users not shown)
Line 13:
AppleScript binds the name '''result''' to the value of the expression most recently evaluated in the current scope.
 
<langsyntaxhighlight lang="applescript">on run
1 + 2
Line 59:
end script
end if
end mReturn</langsyntaxhighlight>
{{Out}}
<pre>{9, 1.732050807569}</pre>
 
The name '''result''' is still bound in this way if the most recently evaluated expression is a script rather than a simple value:
<langsyntaxhighlight lang="applescript">on run
script
-- The given function applied to the value 3
Line 114:
end script
end if
end mReturn</langsyntaxhighlight>
{{Out}}
<pre>{9, 1.732050807569}</pre>
Line 122:
=={{header|Axe}}==
In Axe, evaluated expressions can be "remembered" until the next expression is evaluated.
<langsyntaxhighlight lang="axe">3
Disp *3▶Dec,i</langsyntaxhighlight>
 
Prints:
Line 131:
 
However, attempting to use the result now would result in garbage due to the ▶Dec and Disp commands overwriting the previous result.
 
=={{header|BASIC256}}==
<syntaxhighlight lang="freebasic">function Sum (x, y)
Sum = x + y # using name of function
end function
 
function SumR (x, y)
return x + y # using Return keyword which always returns immediately
end function
 
print Sum (1, 2)
print SumR(2, 3)</syntaxhighlight>
 
=={{header|Clojure}}==
The Clojure REPL has '''*1''' (and also '''*2''' and '''*3''' for the 2nd or 3rd most recent)
<langsyntaxhighlight lang="clojure">
user=> 3
3
Line 141 ⟶ 153:
user=> (Math/pow *2 0.5)
1.7320508075688772
</syntaxhighlight>
</lang>
 
=={{header|Erlang}}==
Line 156 ⟶ 168:
In a stack oriented language like Forth the definition of variables is minimized as much as possible. The closest thing to a topic variable is the use of '''R@'''. This gets the top item from the return stack, which by the way is also used for flow control. It is up to the programmer to keep the stack balanced. In some Forth dialects '''R@''' and '''I''' are identical. '''I''' is used as a loop index, e.g.
 
<langsyntaxhighlight lang="forth">: myloop 11 1 do i . loop cr ; myloop</langsyntaxhighlight>
 
Which will print all numbers from 1 to 10. A typical use of '''R@''' is illustrated here:
 
<langsyntaxhighlight lang="forth">: ^2 dup * ;
: sqrt 0 tuck ?do 1+ dup 2* 1+ +loop ;
: topic >r r@ ^2 . r@ sqrt . r> drop ;
 
23 topic</langsyntaxhighlight>
 
The word '''>R''' places the item on the return stack and the word '''R>''' retrieves it from the return stack - an experienced Forth programmer would optimize this definition even further. Note that for technical reasons all words listed cannot be used outside definitions, so it may be argued that Forth doesn't have topic variables.
Line 175 ⟶ 187:
Alternatively, the keyword 'Function' can itself be used as an implicitly defined variable and behaves in exactly the same way as the function's name when used in this role. Similarly, the keywords 'Property' or 'Operator' can be used to return values from properties or operators respectively.
 
<langsyntaxhighlight lang="freebasic">' FB 1.05.0 Win64
 
' Three different ways of returning a value from a function
Line 194 ⟶ 206:
Print Sum2(2, 3)
Print Sum3(3, 4)
Sleep</langsyntaxhighlight>
 
{{out}}
Line 205 ⟶ 217:
=={{header|Go}}==
Go has nothing like this in the bare language, but the template package of the standard library has a similar mechanism. Templates can have named variables, but they also have a cursor, represented by a period '.' and called "dot", that refers to a current value.
<langsyntaxhighlight lang="go">package main
 
import (
Line 237 ⟶ 249:
`))
t.Execute(os.Stdout, "3")
}</langsyntaxhighlight>
{{out}}
<pre>
Line 247 ⟶ 259:
=={{header|Haskell}}==
In Haskell terminal GHCi or WinGHCi, topic variable is called: it.
<syntaxhighlight lang="haskell">
<lang Haskell>
Prelude> [1..10]
[1,2,3,4,5,6,7,8,9,10]
Prelude> map (^2) it
[1,4,9,16,25,36,49,64,81,100]
</syntaxhighlight>
</lang>
 
=={{header|J}}==
Line 259 ⟶ 271:
Thus, for example (entirely eliminating the variable representing the argument):
 
<langsyntaxhighlight Jlang="j"> example=: *:, %: NB. *: is square, %: is square root
example 3
9 1.73205</langsyntaxhighlight>
 
Or, if we want to see the dummy variable in place (though still not declared, because there is no point to that):
 
<langsyntaxhighlight Jlang="j"> Example=: verb def '(*: y), (%: y)'
Example 3
9 1.73205</langsyntaxhighlight>
 
Or course, if it's crucial to the concept of topic variables that they not be constrained to definitions of things like functions, then it might be argued that J does not have them.
Line 273 ⟶ 285:
On the third hand, note that "definitions of functions" do not actually need to be associated with names. At worst, some definitions might need to be enclosed in parenthesis:
 
<langsyntaxhighlight Jlang="j"> (*:, %:) 3
9 1.73205</langsyntaxhighlight>
 
And if we were to insist on leaving out functions, it's not clear that there would be much of anything left of the language to be doing anything with. See also Henry Rich's writeup on [http://www.jsoftware.com/docs/help701/jforc/tacit_programs.htm Tacit Programs].
Line 291 ⟶ 303:
=={{header|Julia}}==
Julia REPL has `ans` variable:
<langsyntaxhighlight lang="julia">julia> 3
3
julia> ans * ans, ans - 1
(9, 2)</langsyntaxhighlight>
 
=={{header|Kotlin}}==
The closest thing Kotlin has to a topic variable is the identifier 'it' which implicitly refers to the parameter of a lambda expression when it only has one. As in the case of all other parameters in Kotlin, 'it' is read-only and is in scope until the end of the lambda expression.
<langsyntaxhighlight lang="scala">// version 1.1.2
 
fun main(args: Array<String>) {
Line 306 ⟶ 318:
println(Math.sqrt(it.toDouble()))
}
}</langsyntaxhighlight>
 
{{out}}
Line 347 ⟶ 359:
 
In Nim, the special variable <code>_</code> may be considered as a topic variable. It is mainly used in loops when the value of the counter is not needed, for instance:
<langsyntaxhighlight Nimlang="nim">for _ in 1..10:
echo "Hello World!"</langsyntaxhighlight>
 
Another kind of topic variable is <code>it</code> which is used in expressions in some templates. For instance:
<langsyntaxhighlight Nimlang="nim">import sequtils
let x = [1, 2, 3, 4, 5]
let y = x.mapIt(it * it)
echo y # @[1, 4, 9, 16, 25]</langsyntaxhighlight>
 
=={{header|Oforth}}==
Line 363 ⟶ 375:
 
This will push 3 on the stack and compute sq and sqrt :
<syntaxhighlight lang Oforth="oforth">3 dup sq swap sqrt</langsyntaxhighlight>
 
=={{header|PARI/GP}}==
 
gp is a REPL for GP, within which <code>%</code> can be used to refer to the last result.
<langsyntaxhighlight lang="parigp">3
[sqrt(%),%^2]</langsyntaxhighlight>
{{out}}
<pre>%1 = 3
Line 378 ⟶ 390:
It is the default parameter for loops, and some functions e.g. 'sqrt':
 
<langsyntaxhighlight Perllang="perl">print sqrt . " " for (4, 16, 64)</langsyntaxhighlight>
{{out}}
<pre>2 4 8</pre>
Line 386 ⟶ 398:
and the 'local' keyword is needed to enable loops to nest.
 
<langsyntaxhighlight lang="perl">for (1..2) {
print "outer $_:\n";
local $_;
Line 393 ⟶ 405:
}
print " fini\n";
}</langsyntaxhighlight>
{{out}}
<pre>outer 1:
Line 402 ⟶ 414:
=={{header|Phix}}==
The closest thing would be to declare a variable with just an underscore as its identifier.
<!--<syntaxhighlight lang="phix">(phixonline)-->
<lang Phix>object _
<span style="color: #008080;">with</span> <span style="color: #008080;">javascript_semantics</span>
_ = 3
<span style="color: #004080;">object</span> <span style="color: #000000;">_</span>
?_
<span style="color: #000000;">_</span> <span style="color: #0000FF;">=</span> <span style="color: #000000;">3</span>
?_*_</lang>
<span style="color: #0000FF;">?</span><span style="color: #000000;">_</span>
<span style="color: #0000FF;">?</span><span style="color: #000000;">_</span><span style="color: #0000FF;">*</span><span style="color: #000000;">_</span>
<!--</syntaxhighlight>-->
{{out}}
<pre>
Line 413 ⟶ 428:
 
=={{header|PicoLisp}}==
<langsyntaxhighlight PicoLisplang="picolisp">PicoLisp sets the value of the variable (symbol) '@' to the result of
conditional and controlling expressions in flow- and logic-functions (cond, if,
and, when, while, etc.).
Line 421 ⟶ 436:
 
For example, to read the current input channel until EOF, and print the square
of every item which is a number:</langsyntaxhighlight>
Test:
<langsyntaxhighlight PicoLisplang="picolisp">(while (read)
(when (num? @)
(println (* @ @)) ) )
Line 431 ⟶ 446:
xyz # Not a number
3 # Number
9 # -> print square</langsyntaxhighlight>
 
=={{header|PowerShell}}==
Line 440 ⟶ 455:
 
The most common use is in the <code>ForEach-Object</code> cmdlet:
<syntaxhighlight lang="powershell">
<lang PowerShell>
65..67 | ForEach-Object {$_ * 2} # Multiply the numbers by 2
65..67 | ForEach-Object {[char]$_ } # ASCII values of the numbers
</syntaxhighlight>
</lang>
{{Out}}
<pre>
Line 454 ⟶ 469:
</pre>
Using <code>Where-Object</code> to filter the odd numbers from an array:
<syntaxhighlight lang="powershell">
<lang PowerShell>
65..67 | Where-Object {$_ % 2}
</syntaxhighlight>
</lang>
{{Out}}
<pre>
Line 463 ⟶ 478:
</pre>
Using <code>Format-Wide</code> to force an array into columns:
<syntaxhighlight lang="powershell">
<lang PowerShell>
65..70 | Format-Wide {$_} -Column 3 -Force
</syntaxhighlight>
</lang>
{{Out}}
<pre>
Line 474 ⟶ 489:
=={{header|Python}}==
Pythons REPL has '''_'''.
<langsyntaxhighlight lang="python">>>> 3
3
>>> _*_, _**0.5
(9, 1.7320508075688772)
>>> </langsyntaxhighlight>
 
=={{header|Racket}}==
Line 484 ⟶ 499:
Racket doesn't have a "built-in" concept of a topic variable, but one is easy to add to the language with some macros. In fact, the subject of adding such a facility to a language using a hygienic macro facility is a very popular topic in some macro circles, and Racket can do it very well using syntax parameters. In the following there is a demonstration of two implementation approaches, the first uses a "parameter" -- a runtime value that is bound to a value in some dynamic extent, and the second uses a "syntax parameter" which is something that refers indirectly to a plain binding, and this binding can be adjusted by macros to point at an existing "real" binding. See the end of the code for usage samples. (Note that there is no point to talk about how these things behave wrt scope: since Racket is flexible enough to implement these with very different scopes...)
 
<langsyntaxhighlight lang="racket">
#lang racket
 
Line 542 ⟶ 557:
)
(require 'sample2)
</syntaxhighlight>
</lang>
 
=={{header|Raku}}==
Line 549 ⟶ 564:
As in Perl, in Raku the topic variable is $_. In addition to a direct assigment, it can be set with the 'given' or 'with' keywords, or by some iteration operator ('for', 'map' etc). A method can be called from it with an implicit call:
 
<syntaxhighlight lang="raku" perl6line>$_ = 'Outside';
for <3 5 7 10> {
print $_;
.³.map: { say join "\t", '', $_, .², .sqrt, .log(2), OUTER::<$_>, UNIT::<$_> }
}</langsyntaxhighlight>
{{Out}}
<pre>3 27 729 5.196152422706632 4.754887502163469 3 Outside
Line 567 ⟶ 582:
=={{header|REXX}}==
With this new definition of topic variables, the closest thing REXX has to a topic variable is probably function/subroutine arguments being "passed" to the target function/subroutine/routine/procedure.
<langsyntaxhighlight lang="rexx">/*REXX program shows something close to a "topic variable" (for functions/subroutines).*/
parse arg N /*obtain a variable from the cmd line. */
call squareIt N /*invoke a function to square da number*/
Line 573 ⟶ 588:
exit 0 /*stick a fork in it, we're all done. */
/*──────────────────────────────────────────────────────────────────────────────────────*/
squareIt: return arg(1) ** 2 /*return the square of passed argument.*/</langsyntaxhighlight>
{{out|output|text=&nbsp; when using the input of: &nbsp; &nbsp; <tt> 12 </tt>}}
<pre>
Line 580 ⟶ 595:
 
=={{header|Ring}}==
<langsyntaxhighlight lang="ring">
see "sum1 = " + sum1(1,2) + nl
see "sum2 = " + sum2(2,3) + nl
Line 590 ⟶ 605:
func sum2 (x, y)
return x + y
</syntaxhighlight>
</lang>
Output:
<pre>
Line 600 ⟶ 615:
In Ruby the topic variable is $_ (same as Perl).
 
<langsyntaxhighlight lang="ruby">while DATA.gets # assigns to $_ (local scope)
print # If no arguments are given, prints $_
end
Line 606 ⟶ 621:
This is line one
This is line two
This is line three</langsyntaxhighlight>
 
{{out}}
Line 615 ⟶ 630:
</pre>
'''example:'''
<langsyntaxhighlight lang="ruby">DATA.gets
p [$_.to_i ** 2, Math.sqrt($_.to_i)] #=> [9, 1.7320508075688772]
__END__
3</langsyntaxhighlight>
The style of programming using $_ as an implicit parameter is gradually losing favor in the Ruby community.
 
=={{header|Scala}}==
<langsyntaxhighlight lang="scala">object TopicVar extends App {
class SuperString(val org: String){
def it(): Unit = println(org)
Line 634 ⟶ 649:
Seq(4).foreach { it => println(it)}
Seq(8).foreach { it => println(it + it)}
}</langsyntaxhighlight>
 
=={{header|Sidef}}==
The underscore (''_'') topic variable is defined at compile-time in every block of a program. To call a method on it, we can just use the prefix dot (''.'') operator, followed by a method name, which is equivalent with ''_.method_name''
<langsyntaxhighlight lang="ruby">say [9,16,25].map {.sqrt}; # prints: [3, 4, 5]</langsyntaxhighlight>
 
=={{header|Standard ML}}==
Line 645 ⟶ 660:
expression in the REPL (as opposed to a declaration).
 
<langsyntaxhighlight lang="sml">- 3.0;
val it = 3.0 : real
- it * it;
Line 651 ⟶ 666:
- Math.sqrt it;
val it = 3.0 : real
-</langsyntaxhighlight>
 
=={{header|Tailspin}}==
Line 657 ⟶ 672:
The current value goes through a sequence of transformations and has the new transformed value at each stage of the chain.
To do more things with the same current value, a function/templates (here an inline function/templates) can be used to encapsulate several chains where the same current value is accessed at the start of each chain.
<langsyntaxhighlight lang="tailspin">
3 -> \($-1! $+1!\) -> $*$ -> [$-1..$+1] -> '$;
' -> !OUT::write
</syntaxhighlight>
</lang>
{{out}}
<pre>
Line 671 ⟶ 686:
The shell $? is a kind of limited topic variable that holds the return value of the last function called. However, using it in a function will change its value, so following the echo below, the dollarhook will now contain the return value of zero indicating a successful echo:
 
<langsyntaxhighlight lang="sh">multiply 3 4 # We assume this user defined function has been previously defined
echo $? # This will output 12, but $? will now be zero indicating a successful echo</langsyntaxhighlight>
 
=={{header|VBA}}==
Line 681 ⟶ 696:
 
Note that you can't use a single or double underscore as the variable name for this purpose as they always denote instance or static fields of a class.
<langsyntaxhighlight ecmascriptlang="wren">var T // global scope
 
var doSomethingWithT = Fn.new { [T * T, T.sqrt] }
 
T = 3
System.print(doSomethingWithT.call())</langsyntaxhighlight>
 
{{out}}
Line 695 ⟶ 710:
=={{header|zkl}}==
No topic variable pre se (a variable name can be a single character however), but underscore has a special meaning in some cases. Its use is scoped to the expression it is used in.
<langsyntaxhighlight lang="zkl">a,_,c:=List(1,2,3,4,5,6) //-->a=1, c=3, here _ is used as "ignore"
3.0 : _.sqrt() : println(_) //-->"1.73205", _ (and :) is used to "explode" a computation
// as syntactic sugar
1.0 + 2 : _.sqrt() : _.pow(4) // no variables used, the compiler "implodes" the computation
// --> 9
</syntaxhighlight>
</lang>
 
{{omit from|BASIC}}
Line 709 ⟶ 724:
{{omit from|Free Pascal}}
{{omit from|GUISS|Does not have any variables}}
{{omit from|Microsoft Small Basic}}
{{omit from|OCaml}}
{{omit from|Pascal}}
9,482

edits