Is there a way to export ALL the symbols declared in a module? Just to avoid writing them all under export.

I would prefix the module name before the functions you are using when developing (or do something like const m = MyPackage and use m.f(). For improved workflow, I would look at https://github.com/timholy/Revise.jl

[image] kristoffer.carlsson: I would prefix the module name before the functions you are using when developing (or do something like const m = MyPackage and use m.f(). What is the advantage of that, versus exportall? I am just trying to see the downside of having exportall as a feature.

Julz has a function for exporting all vars (that were included using the package) Maybe you can do something like this: https://github.com/djsegal/Julz.jl/blob/master/src/macros/export_all_files.jl

A practice which I like but I see others employ only rarely is putting export statements immediately following definitions like so f(x::AbstractFloat) = # do some stuff function f(x::Complex{<:AbstractFloat}) # do some other stuff end export f I agree that creating an exportall keyword would b…

[image] djsegal: macro export_all_files(cur_item) all_files = get_all_files(eval(cur_item)) cur_expression = quote end for file in all_files exported_object = Symbol("(file)") cur_block = quote export (esc(exported_object)) end append!(cur_expression.args, cur_block.args) end c…

That does seem good for readability while the code is being written, but I wonder if it will become more difficult for other people (or a future you) to understand what the code does. Looking at a list of exports is one of the ways that I typically start to understand a new package. I think I might…

I haven’t particularly found reading the export lists useful without a good handle on what the functions actually do. Sometimes having argument types is enough for this, but the names alone usually aren’t (for me at least). Granted, it does make it easy to lose track of which functions are being e…

Yea, I felt like exportall was a little dodgy (so I scoped it on files for Julz). I believe the following code does exactly what you want // at least it did in v0.5 https://github.com/djsegal/julz_legacy/blob/master/app/templates/config/export_all_except.jl

The following simple snippet seems to work: module Foo foo(x) = x+1 bar(x) = x-1 # exportall: for n in names(current_module(), true) if Base.isidentifier(n) && n ∉ (Symbol(current_module()), :eval) @eval export $n end …

Exportall?

General Usage

stevengj Split this topic September 25, 2024, 2:06am 23

2 posts were split to a new topic: Warning about variable conflict from module export?

Topic		Replies	Views
Exporting symbols of imported module General Usage	5	1876	January 16, 2019
How to export functions from an array in a module? General Usage question	6	1565	June 13, 2019
[ANN] InlineExports.jl Package Announcements	5	813	March 5, 2019
Exportall might be useful in some (limited) cases? Internals & Design	9	662	May 16, 2022
How to export names from a lower level module without explicitly listing all of them? New to Julia	1	489	August 1, 2020

Exportall?

Related topics