[M3devel] paths too truncated in assertion failures

[Olaf Wagner]

On Sat, 29 Aug 2015 22:12:37 +0000
Jay K <jay.krell at cornell.edu> wrote:

> These messages:
> ****** runtime error:***    <*ASSERT*> failed.***    file "../src/convert/Convert.m3", line 47***
> 
> 1) It should really be a full path.
> I know people will disagree with me.You want more commonality across machines.I'm not sure that is worth it.In particular, debuggers always work more easily with full paths, for local private builds.Hopefully for debugging someone else's, some search pathwith "prefix replacement" is viable.But debugging your own build is more common and ideallyno special setting is needed to make that work.
> Yes, full paths could "leak" across machines but I think that is ok.
> I did work on this long ago but people disagreed with at the time.

I'd vote for full absolute path.

Olaf
-- 
Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com 
               Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194