From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Berek" To: , "Syd Polk" Subject: Re: SN Printing Under WIN/NT Date: Thu, 05 Oct 2000 13:13:00 -0000 Message-id: <007001c02f08$b755c7f0$7113a8c0@concord.com> References: <5D2A198567EED311BD0F009027A25C87402387@SRVMAIL-ANN> <4.2.0.58.20001004102624.00dad380@pop.cygnus.com> <4.2.0.58.20001005120625.00db3b10@pop.cygnus.com> X-SW-Source: 2000-q4/msg00024.html Thank you [smile]. I really love SN. If you guys manage to clean up the C++ parser so that it's as reliable as a compiler (the closer to 100%, the better off we'll be...we absolutely have to have accurate xrefs), this product will be a developer's "dream come true". ----- Original Message ----- From: "Syd Polk" To: "Berek" ; Sent: Thursday, October 05, 2000 15:08 Subject: Re: SN Printing Under WIN/NT > At 04:26 PM 10/4/00 -0400, Berek wrote: > >Lot's of problems printing hierarchy and cross reference charts under NT. I > >have SN installed on 1/2 dozen PC's. Some use Postscript drivers, others > >PCL, some use both. All have same results printing on 1/2 dozen networked > >printers. Basically, printing is garbled: letters, symbols, and lines > >overlaying each other. Have to resort to doing NT alt-print screen and > >pasting into MS Word, then printing from Word. > > The real problem is that there are no font preferences that just apply to > printing, and the fonts for screen and printing don't match very well. We > need to do some work at some point cleaning this up, as well as an overall > preferences rewrite. > > > >In Class view, C++ class members that are "private" have symbol (transparent > >diamond) for "public". Private members should have no symbol at all. Both > >public and private have the public symbol. > > > >I'm concerned about comments made by SN Development (Syd Polk?) about > >priority given to Perl parser. I know of more than 1/2 dozen companies in my > >area that have been forced to scale back use of SN because of many problems > >with C++ parser: 3Com, Lucent, Cienna, Concord Communications, Broadband > >Access Systems, Cisco, Fidelity... Unless C++ parsing bugs are fixed, SN > >cannot be relied upon as a development tool. We desparately need accurate > >cross references. Those of us that us SN are forced to fall back on grep's. > >Please review your priorities. > > C++ parser is a high priority; we use it internally. > > Thanks for your feedback; it really is appreciated. > > Syd Polk spolk@redhat.com > Engineering Manager +1 415 777 9810 x 241 > Red Hat, Inc. > > > > >