JS strict warnings in gpsee.js

[Christoph Dorn]

See: https://gist.github.com/1258017

JSLint will hurt your feelings in more than one way

I don't have an easy way to filter duplicates

Christoph

[Wes Garland]

What's gpsee.js?

Wes

--
Wesley W. Garland
Director, Product Development
PageMail, Inc.
+1 613 542 2787 x 102

[Christoph Dorn]

Hmm. Good point. The line numbers threw me off. It's the loader
adapter for gpsee. Never mind, I can fix these.

The line numbers must be from eval()ed code.

I don't think the approach taken here
http://gpsee.blogspot.com/2010/12/wrapped-modules-with-gpsee-02-gsr-10.html
has any benefit for the loader.

What I need is to eval() code in a way that it will keep track of file
and line info properly especially for stack traces. Would
require("gpsee").include() do that? Can I add something to the module
source before eval()ing it?

Christoph

On Oct 2, 5:09 pm, Wes Garland <w...@page.ca> wrote:
> What's gpsee.js?
>
> Wes
>

[Wes Garland]

On 2 October 2011 20:37, Christoph Dorn <chri...@christophdorn.com> wrote:

What I need is to eval() code in a way that it will keep track of file
and line info properly especially for stack traces. Would
require("gpsee").include() do that?

I'm about 98% sure it would.
 

Can I add something to the module
source before eval()ing it

There is an @line syntax you can put in comments for Firefox -- you should be able to use it in gsr if you add | JSOPTION_ATLINE to gsr.c right where it also turns on JSOPTION_JIT.  If you try this and like it, please provide feedback and we will consider it for inclusion in the mainline.

Wes