To: cygwin AT cygwin DOT com
From: Nate Thern <nthern AT yahoo DOT com>
Subject:  Re: building (porting) c++ project w/ deprecated features -- did I do this right?
Date: Tue, 4 Apr 2006 15:26:52 +0000 (UTC)
Lines: 14
Message-ID:  <loom.20060404T163942-382@post.gmane.org>
References:  <040420060252 DOT 19335 DOT 4431DF500009BCA400004B8722007358340A050E040D0C079D0A AT comcast DOT net>
Mime-Version:  1.0
Content-Type:  text/plain; charset=us-ascii
Content-Transfer-Encoding:  7bit
User-Agent: Loom/3.14 (http://gmane.org/)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Eric Blake <ericblake <at> comcast.net> writes:
> You are
> better off teaching your application about modern C++, and sending those
> patches back upstream to the "C Scripting Language" project.
Agreed. I'm just an engineer and self-taught C programmer who regularly 
compiles his own stuff on cygwin when it's not in the standard distribution. 
I'm usually pretty successful at resolving problems, but this CSL build sucked 
me into a downward spiral of little fixes that never did end up working.

If I take the big picture approach, I will have a lot to learn. I'm strictly a 
K&R C guy, I don't know or do etags, autoconf, gdb, etc. I'm probably long 
overdue to learn some of these tools. If I take this on, what resources are 
there to help me learn to code in the gnu style, and learn modern C++? (the 
best my library has is Stroustrup, 1997)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/