From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 11 06:33:33 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C994137B404 for ; Fri, 11 Jul 2003 06:33:33 -0700 (PDT) Received: from mail.rdstm.ro (mail.rdstm.ro [193.231.233.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81F2D43FD7 for ; Fri, 11 Jul 2003 06:33:32 -0700 (PDT) (envelope-from aanton@reversedhell.net) Received: from reversedhell.net (casa_auto [81.196.32.25]) by mail.rdstm.ro (8.12.9/8.12.1) with ESMTP id h6BDXUjd013623; Fri, 11 Jul 2003 16:33:31 +0300 Message-ID: <3F0CC367.3040908@reversedhell.net> Date: Thu, 10 Jul 2003 04:37:43 +0300 From: Alin-Adrian Anton User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030606 X-Accept-Language: en-us, en, ro MIME-Version: 1.0 To: Wes Peters References: <0193271C683D5844A478A359271B8F66147AD8@DC1.dynatec.com> <20030707164832.L49607@beagle.fokus.fraunhofer.de> <3F0790EF.10407@reversedhell.net> <200307102238.02405.wes@softweyr.com> In-Reply-To: <200307102238.02405.wes@softweyr.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: raw socket programming SOLVED X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jul 2003 13:33:34 -0000 Wes Peters wrote: >On Saturday 05 July 2003 08:01 pm, Alin-Adrian Anton wrote: > > >>Yes, it works now, with these includes: >>------------------------------- >>#include >>#include >>#include >>#include >>#include >> >>#include >>#include >>#include >> >>#include >>#include >>------------------------------- >> >> > >Believe it or not, the advice in style(9) is quite helpful in putting >include files in their correct order. I'm so used to doing things in >similar order that I re-wrote your original program as: > >#include >#include > >#include >#include >#include >#include > >#include >#include >#include >#include > >int main() { printf("foo\n"); } > >after grepping for n_long in /usr/include. The order of the netinet >includes; in.h then ip.h then tcp.h, seems logical to me. Perhaps a >(re-) reading of the instructions on include files in style(9) is in >order. > > > Thank you, I just read it. You are right. :-) Alin.