tracker issue : CF-3934762

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

Create & maintain a public specification for CFML

| View in Tracker

Status/Resolution/Reason: Needs Review//

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

Created: 02/05/2015

Components: Documentation

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: 10

And stick to it.

http://en.wikipedia.org/wiki/Programming_language_specification

Even PHP has managed to create itself one.

Why? Because a language just *should*, and it will help the CFML vendors provide a uniform expectation for the CFML community. This in turn will strengthen the CFML community & 3rd-party CFML projects (it'll be easier for a project developer to write cross-compatible code, improving their audience, and encouraging people to undertake projects), and make CFML a more serious prospect for people outside the existing user base.

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

Watson Bug ID:	3934762

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

Attachments:

Comments:

Think this is an excellent idea and something that would make CFML be taken more seriously.
Vote by External U.
8570 | February 05, 2015 08:15:30 AM GMT
Every language should have and follow a spec
Vote by External U.
8571 | February 05, 2015 08:58:18 AM GMT
A language isn't a language until you can say what it is. That takes a formal spec.
Vote by External U.
8572 | February 05, 2015 09:20:57 AM GMT
CFML should absolutely have a specification.
Vote by External U.
8573 | February 05, 2015 11:20:48 AM GMT
Any language claiming to be standardized needs a detailed, public specification. There should never be so much latitude in implementation that one vendor can call their bug a "feature" or "how we unilaterally decided to do it". Anything that doesn't meet the spec exactly is a bug, pure and simple. I believe history has shown that incompatibilities between vendors of a single language has only hurt it. CFML can't afford any more hurt.
Vote by External U.
8574 | February 05, 2015 12:27:20 PM GMT
This is an excellent idea and this will take CFML in the right direction. Every language should have it.
Vote by External U.
8575 | February 05, 2015 10:39:46 PM GMT
Every language should have and follow a specification
Vote by External U.
8576 | February 05, 2015 10:49:46 PM GMT
I am agree with this, language must have some public specification and it should be maintain.
Vote by External U.
8577 | February 05, 2015 10:58:23 PM GMT
Language specification defines the programming language. CFML must have it.
Vote by External U.
8578 | February 05, 2015 10:59:33 PM GMT
+1 ......................
Vote by External U.
8579 | December 04, 2015 05:16:58 AM GMT