On 20.01.20 13:03 , O'Connor, Daniel wrote:
>
>
>> On 20 Jan 2020, at 22:28, joerg van den hoff <[email protected]> wrote:
>> I am running osx 10.15 and have installed tcl 8.6.10 plus tclreadline 2.3.5
with current macports.
>>
>> this works flawlessly, in fact. I am nevertheless asking here since when self-compiling the
exact same tclsh 8.6.10 and trying to use the macports-installed tclreadline together with it, the
latter
>> memory faults in file
>>
>> /opt/local/lib/tclreadline2.3.5/tclreadlineInit.tcl in
>>
>> line 27 `tclreadline::Init'.
>
> What does line 27 look like?
that was the line:
tclreadline::Init
> (or maybe just send the whole file)
>
>> this clearly is not macports problem (since macports-tcl + macports-tclreadline works fine), but
I have so far unsuccessfully tried to find out what causes the problem with the self-compiled tclsh
(I want to test some recent changes to tcl and do want to utilize macports-installed stuff like
tclreadline and tcllib etc. in the process).
>>
>> so I would appreciate any hints from the package maintainers of tcl and tclreadline what I am
doing wrong here?
>
> Seems pretty weird, it's not like tclreadline has had many changes or
anything..
it is maybe not tclreadline's own fault, but I am not sure. I also asked at Tcl lang, but no clear
solution so far:
https://groups.google.com/forum/#!topic/comp.lang.tcl/jCVQ8dTWyxI
I presume somehow there must be a difference between the self-compiled tclsh 8.6.10 and the one
installed by macports and tclreadline does not hook into both in the same way. but I do not
understand what the difference might be...
I so far would not have expected that I can use the package only with a single unique instance of
tclsh...
>
> --
> Daniel O'Connor
> "The nice thing about standards is that there
> are so many of them to choose from."
> -- Andrew Tanenbaum
>
>
