tracker issue : CF-4023312

select a category, or use search below
(searches all categories and all time range)

Expose CFML code parsing rules in a open source and consumable way

| View in Tracker

Status/Resolution/Reason: Needs Review//

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 07/21/2015

Components: Language, Wishlist

Versions: 11.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 16

I was just reading some comments from Chris and Gavin in the CFML slack channel: they're both working on CFML code scanners for various requirements.

This prompted a line of thinking.

One thing various third-parties seem to have a hell of a time doing is to reliably parse CFML with any degree of quality. I’m thinking of things like CFEclipse or the CFML plug-in to SublimeText. Or the half-implemented one for Brackets. And I think there’s another half-implemented one for IntelliJ too? None of them work 100% (varying from probably 50-90%, I s’pose). Also the varScoper project tries hard to parse CFML, but does struggle quite a bit in places.

Obviously Adobe can parse CFML with 100% success, as they manage to compile our code.

Would it be something for them to do to release a language parsing library that encapsulates all the rules for all of CFML, but in an open source and publicly consumable sort of way?

Now I *have no idea* how this would work, as I have never looked into language parsing before, nor have I had any need to really. However this sort of thing really might help those bods out there who *are* into that sort of thing.

I’m absolutely certain there are a bunch of people in the community who do know exactly how such a thing would best work, and no-doubt they would have oars to put in here?

Adobe might be thinking "where’s the buck in this for us?". Whilst it’s not the sort of feature that will directly translate into $$$ going into the Adobe coffers, it will enable the community to do more work to make CFML a more appealing prospect for people to use, which in turn *might* help maintain CFML developer retention, which might help prolong CFML as a viable concern.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4023312

External Customer Info:
External Company:  
External Customer Name: Adam
External Customer Email:  
External Test Config: My Hardware and Environment details:



There always seem to be an axe hovering over the neck for Coldfusion as the most viable option. I agree with Adam, that projects like this indirectly benefit Adobe.
Vote by External U.
6547 | July 21, 2015 02:49:50 AM GMT
Parsing rules would be terrific to have for lots of reasons, but community built code quality scanners would be top of the list and this would also help with building IDE plug-ins for the various IDEs which support CFML. Huge +1 to this.
Vote by External U.
6548 | July 21, 2015 08:10:22 AM GMT
+1 Code scanning as part of a continuous integration process is greatly beneficial to promote standards and higher performing code by recognizing use of older less performing code. It would also be useful to scan for deprecated and obsolete tags and functions. This would allow for the community to move away from legacy code that should not be used anymore, and although very idealistic, if everyone did it, Adobe could start cleaning up the language of code that should be moved away from.
Vote by External U.
6549 | July 21, 2015 08:36:40 AM GMT
The code analyzer already exists, it shouldn't be too hard to open that out and allow custom rules etc. The big win here I see is security scans, to look out for known vulnerability paths, enforce owasp top 10 etc Would love this. I think it would open a lot up for cfml community. I know there is a cf lint project that is reverse engineering it, so why not help the process
Vote by External U.
6550 | July 21, 2015 08:59:41 AM GMT
Please explain in 25 characters or more how this feature impacts productivity and why you are adding a vote.
Vote by External U.
6551 | July 21, 2015 07:16:56 PM GMT
As stated, having this available would allow the community to build better add-on tools for CFML projects.
Vote by External U.
6552 | July 22, 2015 09:35:44 AM GMT
I can see there would be benefits to this and could also help further enhancements / integrations to the product.
Vote by External U.
6553 | July 23, 2015 01:18:19 AM GMT
Yes! This would enable a whole ecosystem of useful tools built by the community!
Vote by External U.
6554 | July 27, 2015 02:09:48 AM GMT
Adding another +1. I think this would be a huge help in enabling good quality community driven tools for CF.
Vote by External U.
6555 | July 27, 2015 04:27:46 PM GMT
Expose CFML code parsing rules in a open source and consumable way
Vote by External U.
6556 | July 28, 2015 01:17:02 AM GMT
+1 Yes please, this makes total sense!
Vote by External U.
6557 | August 03, 2015 06:06:54 AM GMT
Any updates on this "review" that it needs?
Comment by External U.
6545 | January 25, 2016 08:29:56 AM GMT
This has my vote..................
Vote by External U.
6558 | February 23, 2016 10:16:45 PM GMT
> Any updates on this "review" that it needs? Hello?
Comment by Adam C.
6546 | August 02, 2017 07:03:54 AM GMT