Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!brutus.cs.uiuc.edu!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!smithj
From: SMITHJ@ohstpy.mps.ohio-state.edu
Newsgroups: comp.lang.c++
Subject: New Begginer Questions.
Message-ID: <4202@ohstpy.mps.ohio-state.edu>
Date: 8 Sep 89 17:24:01 GMT
Lines: 35

I'm following this conversation with interest as I am a somewhat experienced
C programmer looking to learn C++.  I have started reading Stroustrup's 1986
book and have found it to be poorly written based on bad program fragments and
unclear notation.  Would it be best for me to put this book down immediatley
and find another?

Two questions:
1. Is the declaration type* var; common in C++ programs as opposed to type *var
   and if so why.  I find that it misleads one to beleave that the declaration
			type* x, y;
   would be interpreted as
			type *x, *y;
   rather than the correct
			type *x, y;
2. Why the addition of the typecast convention type(var) when (type)var 
   already exists. 

-- 
They have one big advantage over us: 
		*they* know where they're going.
Has your family tried 'em, Powdermilk?

/* Jeffery G. Smith, BS-RHIT (AKA Doc. Insomnia, WMHD-FM)       *
 *    The Ohio State University, Graduate Physics Program       *
 *        3193 Smith Lab, Columbus, OH 43210  (614) 292-5321    *
 *    smithj@ohstpy.mps.ohio-state.edu                          */
-- 
They have one big advantage over us: 
		*they* know where they're going.
Has your family tried 'em, Powdermilk?

/* Jeffery G. Smith, BS-RHIT (AKA Doc. Insomnia, WMHD-FM)       *
 *    The Ohio State University, Graduate Physics Program       *
 *        3193 Smith Lab, Columbus, OH 43210  (614) 292-5321    *
 *    smithj@ohstpy.mps.ohio-state.edu                          */