[PATCH] new applet: nmeter + Off Topic

[Michael S. Zick]

On Thu July 6 2006 13:39, you wrote:
> On Thu, 6 Jul 2006, Michael S. Zick wrote:
> 
> > On Thu July 6 2006 12:05, Rob Landley wrote:
> > > On Thursday 06 July 2006 11:49 am, Bernhard Fischer wrote:
> > > > Looks better, yes. Still should there be the possibility to turn 2.6 or
> > > > 2.4 support completely off? It would save at lease the int if not more..
> > >
> > > If we add a global "enable 2.4 support" switch, then we should remember this
> > > is here.
> > >
> > > I'm on the fence about whether a global "enable 2.6 support" switch makes
> > > sense.  Considering it won't ship in a release before December, so it's
> > > effectively 2007 by then, I'm leaning against it.  A 2.4 switch gives us
> > > something to hide devfs names and devfsd behind,
> > >
> > Would it make sense then to start adding
> > __attribute__((depreciated)) when code on the "endangered code" list
> > is touched?
> 
> not to be overly pedantic (who, me?) but, once and for all, it's
> "deprecated", not "depreciated."
>
I suppose a simple typo could have prevented you from finding the
documentation.  Notice you will need to enable this warning if wanted.

Here is the option - spelled without the preceding '-':

`deprecated'
     The `deprecated' attribute results in a warning if the variable is
     used anywhere in the source file.  This is useful when identifying
     variables that are expected to be removed in a future version of a
     program.  The warning also includes the location of the declaration
     of the deprecated variable, to enable users to easily find further
     information about why the variable is deprecated, or what they
     should do instead.  Note that the warning only occurs for uses:

          extern int old_var __attribute__ ((deprecated));
          extern int old_var;
          int new_fn () { return old_var; }

     results in a warning on line 3 but not line 2.

     The `deprecated' attribute can also be used for functions and
     types (*note Function Attributes::, *note Type Attributes::.)

 
> yours in pedantry,
> rday
>
No problem, I know I am not the only person to make typos.

> 
> 
Mike