Go to the FreeLists Home Page Home Signup Help Login
 



[openbeosnetteam] || [Date Prev] [09-2002 Date Index] [Date Next] || [Thread Prev] [09-2002 Thread Index] [Thread Next]

[openbeosnetteam] Re: stack

  • From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
  • To: openbeosnetteam@xxxxxxxxxxxxx
  • Date: Mon, 16 Sep 2002 11:19:32 +0200 (MET DST)
On Mon, 16 Sep 2002, Axel =?iso-8859-1?q?D=F6rfler ?= wrote:

> Ingo wrote:
> > I commented out the inclusion of src/add-ons/kernel/drivers/net/
> > stack. 
> > Not only because it doesn't build, but also because the name `stack' 
> > for the net stack executable clashes with the STL header <stack>. 
> > This 
> > is a bit ugly, as it makes all files that include <stack> depend on 
> > the 
> > net stack being built first. I see only two solutions for this 
> > problem: 
> > 1) rename the executable (e.g. `net_stack') or add grist, e.g. `<net>
> > stack', or even better `<user!net>stack' and `<kernel!net>stack' for 
> > the two flavors.
> 
> I somehow dislike the grist :-)

Any reason why? The only one I can think of is, that one has to specify
the full identifier (including grist) on the command line, if building
only that target is desired. But as a work-around pseudo targets can be
added.

> I would prefer to just rename it to net_stack or something like this 
> (like give it a name: "bone", "walter", or whatever ;-))

Then user and kernel land stack must have different names, too. At least
if they are both visible at the same time, i.e. not made mutually
exclusive via an `if ... else'.

CU, Ingo







[ Home | Signup | Help | Login | Archives | Lists ]

All trademarks and copyrights within the FreeLists archives are owned by their respective owners.
Everything else ©2007 Avenir Technologies, LLC.