search for: strbar

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1678264062-154654637-1051422990=:2626055 Content-Type: TEXT/PLAIN; charset=US-ASCII ---1678264062-154654637-1051422990=:2626055 Content-Type: TEXT/PLAIN; charset=US-ASCII;

Hi List, Am trying to customize a legend in trellis: Draws 2x5 lines in 5 colors and 2 linetypes. I would like to add two more items to the legend showing the key for the line types above the colored legend. Any suggestions welcome - thanks Herry ############################# #Following example code: library(gregmisc) trellis.device(bg="white") i1=0 i2=-1.89767506 i3=-1.17087085

...#39;s what we should expect. I believe the current error message format for the existing linkers were set more than 30 years ago when path names and symbol names were much shorter than they are today. If they are short, error messages become something like "src/libfoo/bar.o: undefined symbol: strbar", which is quite easy to read. That is unfortunately no longer the case because we are creating significantly larger programs than a few decades ago and C++ name mangling makes symbol names significantly longer than before. So I would modify your suggested format to use the "note" c...

...ect. > > I believe the current error message format for the existing linkers were > set more than 30 years ago when path names and symbol names were much > shorter than they are today. If they are short, error messages become > something like "src/libfoo/bar.o: undefined symbol: strbar", which is quite > easy to read. That is unfortunately no longer the case because we are > creating significantly larger programs than a few decades ago and C++ name > mangling makes symbol names significantly longer than before. > > So I would modify your suggested format to us...

...t; I believe the current error message format for the existing linkers were >> set more than 30 years ago when path names and symbol names were much >> shorter than they are today. If they are short, error messages become >> something like "src/libfoo/bar.o: undefined symbol: strbar", which is quite >> easy to read. That is unfortunately no longer the case because we are >> creating significantly larger programs than a few decades ago and C++ name >> mangling makes symbol names significantly longer than before. >> >> So I would modify your su...

Folks, I'd like propose a new error message format for LLD so that error message for undefined or duplicated symbols are more informative and easy to read. Below are examples of the current error messages (note that characters in red are actually red on terminal): *Undefined symbols* /ssd/clang/bin/ld.lld: error: /ssd/llvm-project/lld/ELF/Writer.cpp:207: undefined symbol