How come that I always find another solution just moments _after_ I posted into
this forum ... ;)


The 'documentation != implementation' issue still exists, but I can suppress
those lint warnings I want to get rid of by using the "ignoreUndefined" hints.


Another founding was, that the 'lint-hint' comments have to be alone in one
line, else they are not recognized.
It seems to me that the regular expression in [4] is

Example:

  This works:

  <code>
    /**
     * @lint ignoreUndefined(google)
     */
    doFoo : function (fooPar) {
      this.__googleMapsObject.setMapType(google.maps.SATELLITE_MAP);
    }
  </code>

  while this doesn't:

  <code>
    /** @lint ignoreUndefined(google) */
    doFoo : function (fooPar) {
      this.__googleMapsObject.setMapType(google.maps.SATELLITE_MAP);
    }
  </code>



So to sum it up:

1. The "@lint ignoreGlobal(VARIABLE_NAME)" doc hint is not really needed,
2. but the documentation might need an update.
3. It would be nice if the 'lint-hint' parser would allow those 'one-liners',
   but its definitely no must!



/Peter


-------- Original --------
From: Peter Schneider
Date: 08.04.2010 17:33

> Hi there,
> 
> I found that the doc-comment "@lint ignoreGlobal(VARIABLE_NAME)" is not 
> working
> (anymore) in qooxdoo 1.0.x.
> 
> Either the documentation[1] is out of date or the implementation is missing ;)
> 
> If this feature will not be (re-)implemented, the 'application-global'[2]
> setting of "lint-check" in the generator configuration[3] is the weapon of
> choice, right?
> 
> 
> My argument for the "ignoreGlobal":
> I would like to fine-control where a global variable is allowed to use and
> where not. Think of this class/module-hierarchy example:
> 
> AbstractMap        // no globals allowed!
>   +- GoogleMap     // @lint ignoreGlobal(google.*)
>   +- OpenLayersMap // @lint ignoreGlobal(OpenLayers.*)
>   +- AnyOtherMap   // @lint ignoreGlobal(whatever.*)
> 
> Where the wildcard(*) in the VARIABLE_NAME is not needed for me, what I mean 
> by
> this 'notation' is, that I can allow the use of a global on a per-method base,
> or on a per-module base, etc.
> 
> I would love to see that 'feature' implemented.
> 
> Regards,
>   Peter
> 
> ----
> [1] http://qooxdoo.org/documentation/1.0/tool/source_code_validation
> [2] with 'application-global' I mean: Once "foo2 is an "allowed-global", it 
> can
>     be used everywhere! Even where it shouldn't...
> [3] http://qooxdoo.org/documentation/1.0/tool/generator_config_ref#lint-check

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to