Re: #1788: Static link file contains bogus unit names

[Chicken Trac]

#1788: Static link file contains bogus unit names
-------------------------------------+-------------------------------------
            Reporter:  sjamaan       |      Owner:  felix winkelmann
                Type:  defect        |     Status:  accepted
            Priority:  major         |  Milestone:  5.3
           Component:  compiler      |    Version:  5.2.0
          Resolution:                |   Keywords:  static linking,
Estimated difficulty:  medium        |  dependencies
-------------------------------------+-------------------------------------

Comment (by evhan):

 > Thanks, Evhan. But I think `required-libraries` has a clear meaning and
 only things should appear in this list that are both truly required and
 libraries. `##sys#process-require` is the right place to make the
 distinction.

 My thinking was that it would include "libraries that have been required",
 as in, "libraries for which a `##core#require` form has been processed",
 similar to how `linked-libraries` contains "libraries that have been
 linked" or `used-units` contains "units that have been used". Although
 there isn't any filtering done for those lists, so they aren't really a
 useful comparison in that way.

 Anyway, if the filtering is moved then I think `chicken.load#core-unit?`
 should go away completely, since this is the only reason it exists. I just
 wanted to mention that when Peter described the solution below, it is
 something that already exists and just needs extension:

 > A more elaborate but arguably cleaner fix would involve adding a
 predicate to eval.scm check whether it's part of core-unit-requirements or
 builtin-features or core-units, and use that as a guard around that set!
 mentioned above.

-- 
Ticket URL: <https://bugs.call-cc.org/ticket/1788#comment:6>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.