Re: [Chicken-janitors] #1505: Trace output is messy for eggs

[Chicken Trac]

#1505: Trace output is messy for eggs
-------------------------------------+-------------------------------------
            Reporter:  sjamaan       |      Owner:
                Type:  defect        |     Status:  new
            Priority:  not urgent    |  Milestone:  5.1
  at all                             |
           Component:  extensions    |    Version:  5.0
          Resolution:                |   Keywords:  trace output, messy
Estimated difficulty:  medium        |
-------------------------------------+-------------------------------------

Comment (by sjamaan):

 The output of chicken-profile goes beyond 80 columns, resulting in hard to
 read output unless I fullscreen the terminal window.

 In CHICKEN 4, it used the pathname relative to the build directory of the
 egg. In CHICKEN 5, the same is true for all user code (and CHICKEN core
 too, if built with debug info, as you can see in the sample output above),
 but traces of procedures in eggs contain absolute pathnames. This is not
 very useful and actively annoying: I really don't care where an egg was
 compiled (and certainly not the full path).

 In the output you also see the module name (because it's fully qualified),
 which is enough information for me when I'm profiling my code.

 I don't see why a relative pathname would be of little use: the place
 where an egg is installed from is irrelevant, the only thing that matters
 is ''where in the egg'' that file exists. The full path to the chicken-
 install cache directory or the place where I happened to have the egg
 checked out doesn't tell me anything.

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