File tree Expand file tree Collapse file tree 1 file changed +11
-11
lines changed Expand file tree Collapse file tree 1 file changed +11
-11
lines changed Original file line number Diff line number Diff line change @@ -490,8 +490,8 @@ Then use the tag you like and pick the symbol by its name.
490
490
my &escape-uri = URI::Escape::EXPORT::DEFAULT::<&uri_escape>;
491
491
492
492
Be careful I < not > to put C < sub EXPORT > after L « C < unit > declarator|/syntax/unit» .
493
- If you do so, it'll become just a sub inside your package, rather than the special
494
- export sub:
493
+ If you do so, it'll become just a sub inside your package, rather than the
494
+ special export sub:
495
495
496
496
= for code :solo
497
497
unit module Bar;
@@ -501,17 +501,17 @@ sub EXPORT { %(Foo => &say) } # WRONG!!! Sub is scoped wrong
501
501
sub EXPORT { %(Foo => &say) } # RIGHT!!! Sub is outside the module
502
502
unit module Bar;
503
503
504
- = head2 Finding modules
504
+ = head2 Finding installed modules
505
505
506
- It is up to the module installer to know where C < compunit > expects modules to
507
- be placed. There will be a location provided by the distribution and in the
508
- current home directory. In any case, letting the module installer deal with
509
- your modules is a safe bet.
506
+ It is up to the module installer to know where C < compunit > expects modules to be
507
+ placed. There will be a location provided by the
508
+ L < distribution|/syntax/$%3FDISTRIBUTION > and in the current home directory. In
509
+ any case, letting the module installer deal with your modules is a safe bet.
510
510
511
- = begin code :lang<shell>
512
- cd your-module-dir
513
- zef --force install .
514
- = end code
511
+ = begin code :lang<shell>
512
+ cd your-module-dir
513
+ zef --force install .
514
+ = end code
515
515
516
516
X < |use lib >
517
517
A user may have a collection of modules not found in the normal ecosystem,
You can’t perform that action at this time.
0 commit comments