Null pointer on !C::b
#708
Comments
|
From what I can tell, this is an issue stemming from cfparser and it being able to deal with static constructs and notation. Is this Lucee or does ACF support static as well these days? I've tried to make some inroads on that a while ago but struggled and ended up realising that in an ideal world and a much better solution would be CFLint sitting on top of the Lucee parser (and have started having discussions with Micha around that). |
|
ACF also supports statics afaik.
Mark Drew
… On 29 Jun 2021, at 21:35, Kai Koenig ***@***.***> wrote:
From what I can tell, this is an issue stemming from cfparser and it being able to deal with static constructs and notation.
Is this Lucee or does ACF support static as well these days?
I've tried to make some inroads on that a while ago but struggled and ended up realising that in an ideal world CFLint would sit on top of the Lucee parser (and have started having discussions with Micha around that).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
|
@TheRealAgentK , using a 'live' parser like Lucee's makes sense. The language is evolving a rapid pace - and Lucee is on the bleeding edge. |
|
I ran into this today while using a static method reference as the default value on a function argument. For example, cflint cannot parse the file at all if it contains this method (specifically the default value for the options argument) CFLint ignoring the line with the static reference doesn't make a difference, it still throws a null pointer exception on the first line of the file (which is just a comment). If I update the method to this, it still works as expected and cflint (or cfparser) no longer bombs on it. Full stack below (https://github.com/jsteinshouer/commandbox-cflint/blob/master/commands/cflint.cfc#L347) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running CFLint for the first time, I was getting a null pointer exception on one of my files. I managed to distill it down to this repro case:
Where C is a CFC, and b is a static boolean value... the real-world case was far more complicated than this, but this reproduces it for me. The real-world code is legit and works fine. The name of the component and the static variable are longer than single-characters IRL.
Note that the
!is significant. No null pointer unless it is there. n the real code it is in the same expression as the static reference, but not immediately adjacent to it. Something like this:I have other static references in the file, and they do not cause this issue.
I am running CFLint via the commandbox module (https://www.forgebox.io/view/commandbox-cflint). I strongly suspect this is coming from CFLint though, given the nature of it.
If you can't repro from just that, lemme know and I'll provide more info. You'll need to tell me what additional info you need though, as I've been using this thing for about 30min now, and am completely new to it.
Cheers!
The text was updated successfully, but these errors were encountered: