From cgunning@hpbs3943.boi.hp.com Fri Nov 15 17:33:05 PST 1996 Received: from paloalto.access.hp.com (paloalto.access.hp.com [15.254.56.2]) by dworshak.cs.uidaho.edu (8.7.5/1.1) with ESMTP id RAA21722 for <jone9333@cs.uidaho.edu>; Fri, 15 Nov 1996 17:33:02 -0800 (PST) Received: from hpbs3943.boi.hp.com (hpbs3942.boi.hp.com) by paloalto.access.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA003617980; Fri, 15 Nov 1996 17:33:01 -0800 Received: by hpbs3943.boi.hp.com (1.37.109.18/15.5+IOS 3.22) id AA213917980; Fri, 15 Nov 1996 18:33:00 -0700 From: Chris Gunning <cgunning@hpbs3943.boi.hp.com> Message-Id: <199611160133.AA213917980@hpbs3943.boi.hp.com> Subject: Re: CCA beta - perl 5.000 won't do. To: jone9333@cs.uidaho.edu Date: Fri, 15 Nov 96 18:32:59 MST Cc: cgunning@hpbs3943.boi.hp.com, tpearse@boi.hp.com In-Reply-To: <199611152039.MAA07666@hidden.cs.uidaho.edu>; from "Sean Jones" at Nov 15, 96 12:39 (noon) Mailer: Elm [revision: 70.85] Status: RO Sean, > Dear HP beta-testers, > > We were mistaken when we said that CCA would work with perl 5.x . > > Perl 5.000 has some serious bugs in its array handling. This caused some > very strange errors when Troy attempted to use CCA under this version of > Perl. > > CCA *is* tested on Perl 5.001 and Perl 5.002, both of which will work fine. Fortunately I'm already using Perl 5.001. I ran some of our include files through it without problem. Some quick feedback: - "cca -h" output could be made a lot more helpful. - Could you show the nesting level in the Complete Conditional Logic Listing? Either something like: Line# CCD Expression --------------------------------------------------- 20 #ifndef MYFILE_H 28 .#ifdef SYSTEM_SIMULATOR 32 ..#ifdef A_VALUE 36 ..#elif SOME_OTHER_VALUE 40 ..#else 44 ..#endif 48 .#endif 50 .#ifndef MILLISEC 52 .#endif 74 #endif or Line# Lvl CCD Expression --------------------------------------------------- 20 1 #ifndef MYFILE_H 28 2 #ifdef SYSTEM_SIMULATOR 32 3 #ifdef A_VALUE 36 3 #elif SOME_OTHER_VALUE 40 3 #else 44 3 #endif 48 2 #endif 50 2 #ifndef MILLISEC 52 2 #endif 74 1 #endif I tried generating a Postscript file from osmsgs.h, which contains 34 lines of conditional compilation logic. The output is way too small to read in Ghostview V1.5, even using Magstep=5 or Zoom. The hardcopy is also difficult to read (4 point text!) I was finally able to view it by converting the Postscript file to a PDF and using Adobe Acroread, which has better zoom capability. Any chance you could generate a PDF file directly? -- Chris G. *************************************************************************** Chris, > I tried generating a Postscript file from osmsgs.h, which contains 34 > lines of conditional compilation logic. The output is way too small > to read in Ghostview V1.5, even using Magstep=5 or Zoom. The hardcopy > is also difficult to read (4 point text!) > > I was finally able to view it by converting the Postscript file to a > PDF and using Adobe Acroread, which has better zoom capability. Any > chance you could generate a PDF file directly? > > -- Chris G. > The default scaling factor for CCA is to fit everything onto a single page. This is a customer requirement. You can, however, scale your images to several other sizes. You can scale images by inserting a numerical value after the -g on the command line. Ex: cca -f input.c -o output.txt -g4 graph.ps The numbers can be any from 1,2,4,8,16. Inserting the letter p (for page) in place of a number gets you the scaling factor you've been experiencing. The larger the number, the larger the images will appear. A scale factor of -g4 won't be viewable (without magstep) in ghostview, but will be readable when printed. A scale factor of -g8 produces what I think is the minimal size you can actually read in gv without zooming. Sorry, we can't produce PDF files. Sean Jones CS481 B-Team Leader jone9333@cs.uidaho.edu