From owner-freebsd-hackers Tue Sep 19 15:24:49 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA03459 for hackers-outgoing; Tue, 19 Sep 1995 15:24:49 -0700 Received: from vinkku.hut.fi (root@vinkku.hut.fi [130.233.245.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA03454 for ; Tue, 19 Sep 1995 15:24:44 -0700 Received: from lk-hp-20.hut.fi (lk-hp-20.hut.fi [130.233.247.33]) by vinkku.hut.fi (8.6.12/8.6.7) with ESMTP id BAA12539 for ; Wed, 20 Sep 1995 01:24:37 +0300 From: Juha Inkari Received: (inkari@localhost) by lk-hp-20.hut.fi (8.6.12/8.6.7) id BAA29255 for hackers@freefall.freebsd.org; Wed, 20 Sep 1995 01:24:37 +0300 Message-Id: <199509192224.BAA29255@lk-hp-20.hut.fi> Subject: Re: Coding style ( was Re: why is this not a bug in namei?) To: hackers@freefall.freebsd.org Date: Wed, 20 Sep 1995 01:24:37 +0200 (EETDST) In-Reply-To: <199509192128.OAA10722@phaeton.artisoft.com> from "Terry Lambert" at Sep 19, 95 02:28:35 pm X-Mailer: ELM [version 2.4 PL22] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 341 Sender: owner-hackers@FreeBSD.org Precedence: bulk One reason to be carefull with goto statements is C++ compability. In C++ it is illegal to jump over variable initialization. For example, the code below is valid C, but not valid C++. if (1) { goto jump; } while (1) { int b = 1; jump: /* stuff ... */ } This is, of course, bad practise in plain C, too.