Private procedures cause a link error #132

Open
opened 2025-08-14 00:48:40 +02:00 by belka · 0 comments
Owner
  1. One module doesn't export a procedure f (but defines it).
  2. Another module imports the first module and uses f.
  3. f should be reported as undefined, but it is not reported and the linking fails later.
1. One module doesn't export a procedure `f` (but defines it). 2. Another module imports the first module and uses `f`. 3. `f` should be reported as undefined, but it is not reported and the linking fails later.
belka added the
bootstrap
label 2025-08-14 00:48:40 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: belka/elna#132
No description provided.