Repository navigation
JavaScript debug statements #18851
Description
Activity
we can pretty easily adapt the DTRACE_* macro system, i'd be willing to make a pr
There was some work that went into a
//CHECK(statement);comment that could be enabled.Nice, do you know where I can find some further info about it?
I think our JS files are preprocessed by a python script before ending up in the binary. It might be somewhere inside it?
I think our JS files are preprocessed by a python script before ending up in the binary. It might be somewhere inside it?
The version of
js2c.pyin V8 indeed supports macro expansion (as defined either inline or inmacros.py). It should be easy to select a macro file depending on build mode.I had discussed making debug macro comments with @trevnorris for async-hooks but the idea never got anywhere. I think this would be a good idea for core development/debugging.
Reacted by Ruben Bridgewater and Benjamin Gruenbaum- changed the title
[-]Javascript debug statements[/-][+]JavaScript debug statements[/+]on Feb 19, 2018
I personally would some times like to have some debug calls for internal APIs e.g. the internal errors. It would make the API easier to use by just verifying the input but only when run by our test suite. We are all human and make mistakes. So it should behave similar to a DCHECK in C++ but just in JS. Because I would not want to have those checks run in production.
Do we want to introduce something like that? (Or do we actually already have that and I just missed that?)
I guess there are two ways of implementing something like that:
a) A macro
b) A simple
if (env.NODE_DEBUG_INTERNAL === 'true') {}What do others @nodejs/collaborators think?