File: read_eval_print_loop.txt

package info (click to toggle)
node-stdlib 0.0.96%2Bds1%2B~cs0.0.429-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 421,476 kB
  • sloc: javascript: 1,562,831; ansic: 109,702; lisp: 49,823; cpp: 27,224; python: 7,871; sh: 6,807; makefile: 6,089; fortran: 3,102; awk: 387
file content (752 lines) | stat: -rw-r--r-- 13,251 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
---
name: repl
description: Learn how to use the REPL environment.
---

| \*Tutorial: REPL\s


How to use this tutorial...

• Enter

  ```javascript
  next();
  ```

  followed by \*RETURN\s to advance the tutorial.

---

• At the command prompt, enter

  ```javascript
  pres();
  ```

  followed by \*RETURN\s to see the list of available tutorial commands.

---

• As documented when running \*pres()\s, you can use command shortcuts.
  For example, enter

  ```javascript
  n();
  ```

  followed by \*RETURN\s to advance the tutorial.

---

• Use the up/down arrow keys to cycle through previously run commands.
  Feel free to try using the arrow keys below...

---

• When entering and running commands, the tutorial presentation slide is
  likely to scroll out of view.

  To return to the slide, simply scroll up. :grinning:

---

• As this tutorial is a REPL presentation, enter

  ```javascript
  presentationStop();
  ```

  followed by \*RETURN\s to end this tutorial at any time.

• Enter

  ```javascript
  quit();
  ```

  to exit the REPL altogether.

---

| Enough preliminaries, let's start the tutorial!

---

| This tutorial introduces you to the REPL environment.

---

| REPL stands for \*r\sead-\*e\sval-\*p\srint \*l\soop\s.

---

| A REPL...

\s

--

• ...is an interactive programming environment

--

• ...which receives individual user inputs (e.g., single expressions)

--

• ...evaluates those inputs

--

• ...and returns the result.

---


| Accordingly, an entered program is executed piecewise and sequentially.

---

In this tutorial, you've already been using the REPL when you've advanced
the tutorial and printed the list of available commands.

As another simple example, evaluate the following input

```javascript
1+1
```

--

\s
In this case, we entered `1+1` (user inputs) and instructed the REPL to evaluate
those inputs (\*RETURN\s), and the REPL returned (and printed) the result.

--

\s
After returning the result, the REPL provides another prompt, thus completing
the \*r\sead-\*e\sval-\*p\srint \*l\soop.

---

| REPLs are useful for...
\s

--

• learning programming languages (such as JavaScript)

--

• debugging (including when embedded in running applications)

--

• demos (including live coding)

--

• interactivity (such as during iterative development)

---

To get started using this REPL, a few commands will prove immensely useful.

---

The first command is

```javascript
help()
```

Run the above command to see a list of REPL commands.

---

To see the documentation for a specific REPL alias, provide the alias to the
\*help()\s command.

For example, run

```javascript
help( '{{alias:@stdlib/math/base/special/sin}}' )
```

to see the documentation for the \*{{alias:@stdlib/math/base/special/sin}}\s function.

---

On the previous slide, you specified the alias via a string representing the
alias name.

You can also provide a reference pointing to the aliased value.

For example, run

```javascript
help( {{alias:@stdlib/math/base/special/sin}} )
```

to see the same documentation as before.

---

Additionally, for objects having known methods, you can print method
documentation.

For example, run

```javascript
help( {{alias:@stdlib/random/base/randu}}.factory )
```

to see the \*factory()\s method documentation.

---

Lastly, for select objects having a known constructor, you can provide
instances.

For example, create a \*Float64Array\s

```javascript
var x = new {{alias:@stdlib/array/float64}}( 10 );
```

and then run

```javascript
help( x )
```

which will print the documentation for \*Float64Array\s.

---

The \*help()\s command provides detailed API documentation.

Sometimes, you just want to know the function signature and a brief
description.

For this use case, you can use another command: \*info()\s.

For example, run

```javascript
info( '{{alias:@stdlib/math/base/special/sin}}' )
```

to see abbreviated API documentation for \*{{alias:@stdlib/math/base/special/sin}}\s.

---

Similar to \*help()\s, you can provide a variable reference.

For example, run

```javascript
info( {{alias:@stdlib/math/base/special/sin}} )
```

to see the same abbreviated API documentation.

---

Another useful command is \*example()\s, which runs the example code found in
the documentation printed by \*help()\s.

For example, run

```javascript
example( '{{alias:@stdlib/math/base/special/sin}}' )
```

to run the example code found in the documentation for \*{{alias:@stdlib/math/base/special/sin}}\s.

---

Similarly to \*help()\s and \*info()\s, you can provide a variable reference.

For example, run

```javascript
example( {{alias:@stdlib/math/base/special/sin}} )
```

to again run the example code for \*{{alias:@stdlib/math/base/special/sin}}\s.

---

Finally, two other commands are useful when wanting to resolve aliases and
package implementations.

---

To determine which package corresponds to a specified alias, use
\*alias2pkg()\s.

For example, run

```javascript
alias2pkg( '{{alias:@stdlib/math/base/special/sin}}' )
```

or

```javascript
alias2pkg( {{alias:@stdlib/math/base/special/sin}} )
```

to resolve the package for \*{{alias:@stdlib/math/base/special/sin}}\s.

---

To determine which alias corresponds to a specified package, use
\*pkg2alias()\s.

For example, run

```javascript
pkg2alias( '@stdlib/math/base/special/sin' )
```

to resolve the alias for \*@stdlib/math/base/special/sin\s.

---

When you're working in a REPL, you're often interested in viewing the
results of the previously invoked command.

Accordingly, when you run

```javascript
1+1
```

you should see the result \*2\s.

---

However, at other times you'll want to silence printed output.

To do so, add a \*semicolon\s to any statement.

For example, when you add a semicolon to the previous statement

```javascript
1+1;
```

no result is printed.

---

During iterative development, you'll occasionally forget to assign the
results of the last expression or statement.

Fortunately, the REPL has a special variable which stores the last result:
\*ans\s.

For example, run the previous statement

```javascript
1+1;
```

followed by

```javascript
ans
```

to see that \*ans\s is assigned the value \*2\s.

---

While not encouraged for general use, \*ans\s can be used just like any
other variable within the top-level scope.

---

Another common occurrence during iterative development within a REPL
environment is forgetting variable names or failing to remember what
variables have already been declared.

Thankfully, you can run

```javascript
vars()
```

to return a list of user-defined variable names. For additional variable
details, run

```javascript
help( vars )
```

to see function options.

---

To facilitate working with long variable names and nested property access,
the REPL supports \*TAB\s completion.

For example, enter

```javascript
base.r
```

followed by \*TAB\s to generate a list of auto-completions which begin
with the letter \*r\s.

---

Similarly, if you create a nested object

```javascript
var obj = { 'beep': { 'boop': { 'foo': 'bar' } } };
```

and then enter

```javascript
obj.beep.b
```

followed by \*TAB\s, the nested property \*boop\s should auto-complete.

---

\*TAB\s completion also works with computed properties. For example, enter

```javascript
obj[ 'beep' ][ 'b
```

followed by \*TAB\s to auto-complete the nested property \*boop\s as done
in the previous slide.

---

For select APIs interacting with the filesystem, \*TAB\s completion is
supported for file paths.

For example, enter

```javascript
{{alias:@stdlib/fs/read-file}}.sync( './
```

followed by \*TAB\s to generate a list of applicable file paths.

---

Additionally, \*TAB\s completion is supported for variables defined in a
nested scope.

For example, enter

```javascript
function foo() { var beep = 5; be
```

followed by \*TAB\s to auto-complete the variable \*beep\s.

Similarly, entering

```javascript
function foo( beep ) { console.log( be
```

followed by \*TAB\s auto-completes the parameter \*beep\s.

---

When working in a REPL, you'll often times want to explore and test
functions and workflows using different parameterizations and variable
values.

Managing the various variables can be messy and difficult.

To this end, this REPL introduces the concept of workspaces.

---

A \*workspace\s is simply a named collection of user-defined variables.

---

To print the name of the current workspace, run

```javascript
currentWorkspace
```

Take note of this workspace name.

---

To retrieve a list of all workspaces, run

```javascript
workspaces()
```

---

To either switch to or create a workspace, you can use the \*workspace()\s
command. For example, enter

```javascript
workspace( '
```

followed by \*TAB\s to see a list of existing workspaces to which you can
switch.

---

To switch to the "base" workspace, run

```javascript
workspace( 'base' )
```

If you now run

```javascript
vars()
```

notice that the variables defined in the previous workspace are no longer
present.

Return back to the tutorial workspace.

---

Run the \*help()\s command to see additional workspace-related commands.

---

JavaScript is single-threaded and asynchronous.

To support asynchronous APIs, the REPL supports top-level \*async\s/\*await\s.

---

In Node.js environments supporting \*async\s/\*await\s, run

```javascript
await new Promise((resolve) => setTimeout(() => resolve( 'beep' ), 2000))
```

which will return the resolved value.

---

In older Node.js environments and when using non-promise APIs, you can
invoke a \*__done__\s callback.

For example, define the following function

```javascript
function foo() {setTimeout(() => __done__(null, 'beep'), 2000)};
```

To asynchronously resolve the value, run

```javascript
"async"; foo()
```

where the special directive \*"async";\s indicates that a command is
asynchronous.

---

During iterative development, you'll frequently want to rerun one or more
commands.

For example, let's say you want to simulate the rolling of two fair dice

```javascript
var dice = {{alias:@stdlib/random/base/discrete-uniform}}.factory( 1, 6, {'seed': 1234} );
function roll() { return [ dice(), dice() ]; };
```

To roll the dice, enter the following command one or more times

```javascript
roll()
```

---

To regenerate the same dice roll sequence, run

```javascript
rerun( [ X, Y ] )
```

where \*X\s is the line number where you declared \*dice\s and \*Y\s is
a line number where you invoked \*roll()\s.

\*rerun\s is especially useful for saving keystrokes when rerunning
arbitrary sequences of commands.

---

When working in a REPL, you'll have use cases where you'll want to
encapsulate extended logic in external files.

These files will typically export functionality and/or data which you
can then import into the REPL environment.

For example, open up your favorite editor, create a new file, and paste
the following code

```javascript
function beep() {
    return 'boop';
}

module.exports = beep;
```

---

To load your newly created file, enter

```javascript
var beep = require( './
```

followed by \*TAB\s to use \*TAB\s completion to locate your file.

Once you've resolved the file's path and executed the command, run

```javascript
beep()
```

which should return the value \*'boop'\s.

---

Now modify your file to match the following contents

```javascript
function beep() {
    return 'beepboop';
}

module.exports = beep;
```

Rerun the \*require()\s statement you entered above and run

```javascript
beep()
```

Did the command return \*'beepboop'\s?

---

\*require()\s works by caching the exports of previously required modules.

To explicitly reload your modified file, enter

```javascript
beep = rerequire( './
```

followed by \*TAB\s to use \*TAB\s completion to once again locate your file.

Once you've resolved the file's path and executed the command, run

```javascript
beep()
```

which should return the expected value.

---

For those use cases where you need to reload a module and all of its module
dependencies, use \*deeprerequire()\s.

---

Working in a REPL frequently involves working with data.

To facilitate exploring that data, the REPL provides a plot API.

---

As a simple example, define two 1-dimensional data arrays corresponding
to the x- and y-axis plot data, respectively.

```javascript
var x = {{alias:@stdlib/utils/inmap}}( new {{alias:@stdlib/array/int32}}(100), (v,i) => i );
var y = [ ...{{alias:@stdlib/random/iter/randu}}({'iter':x.length}) ];
```

---

Next, define a new \*Plot\s instance by running

```javascript
var plt = new {{alias:@stdlib/plot/ctor}}( [x], [y] );
```

To view the plot in a separate window, run

```javascript
plt.view( 'window' )
```

---

To further explore the \*Plot\s API, run

```javascript
help( {{alias:@stdlib/plot/ctor}} )
```

---

| \*Congratulations!\s

You've now reached the end of this tutorial.

Hopefully, by now, you've realized how powerful (and fun!) programming in
a REPL can be! :grinning:

---

| Happy REPLing!

---

| The End

---

• To exit this tutorial and return to the "base" workspace, run

  ```javascript
  presentationStop();
  ```

• To exit the REPL altogether, run

  ```javascript
  quit();
  ```