This article is rated Stub-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
There's a reference to "re-source the Norcroft back end" in Tom Crick's 'A GCC Front End for BCPL', which may be worth including. -- Trevj ( talk) 14:35, 16 June 2011 (UTC)
The currently stated site is the most appropriate one I know of. Perhaps there's something more obvious which I've missed. It's not listed there for WP:SPAM puropses, despite such an appearance from the URL. I hope this makes sense. Thanks. -- Trevj ( talk) 22:52, 16 June 2011 (UTC)
This guide published by Castle Technology states it is "Based on a two part article which appeared in both Archive and Acorn User, November/December 2002." Therefore, if anyone reading this has access to the relevant publications it could be useful. I don't know whether they include any extra information, or if it's all in that doc. In any case, Archive and Acorn User would be preferable in terms of reliable sources. -- Trevj ( talk) 13:03, 17 August 2011 (UTC)
Most of which can be seen by just visiting Codemist's website. Norcroft was a licencable C front end developed at the university of Cambridge (and later also at the university of Bath) used in teaching, and Acorn licenced it. It targets many many architectures. The history and architectures sections of this article are completely made up. And many elements in the main section (including ownership etc) are misleading. Also, useful information such as the fact that ARM themselves abandoned the Norcroft frontend for EDG's are missing. Sort it out, guys. — Preceding unsigned comment added by 82.6.165.102 ( talk) 15:53, 20 October 2011 (UTC)
I'm confused. http://www.codemist.co.uk/ncc/index.html says Acorn Computers ARM C Compiler. This is the original ANSI C compiler known as Norcroft C. But that page is titled Codemist Compilers / Norcroft, which implies that all the other compilers (listed beneath Acorn on that page) also fall under the Norcroft title. (Which is ambiguous, if "Norcroft C" refers to the Acorn compiler.) Should there be subheadings within this article for each compiler? I've just emailed Codemist to request input (pointing to WP:COI and WP:V).
Additionally, I think that the 'History' and 'Uses' headings should be retained (perhaps as subheadings within 'Acorn C/C++'). Help:Section states A page can and should be divided into sections [...] Removing section headings could result in unstructured expansion of the article. While I can't find any policy as such, e.g. at MOS:HEAD, the purpose of sections is clearly to structure articles. WP:BODY also states Very short or very long sections and subsections in an article look cluttered and inhibit the flow of the prose. but (with the exception of the 'Architectures' seciton) I wouldn't consider them "very short". So where do we go from here? Thanks. -- Trevj ( talk) 07:49, 21 October 2011 (UTC)
First I should make it clear I am a director of Codemist Ltd who wrote the Norcrift C Compiler and still sell it (see http://codemist.co.ukncc). The main page seems to talk as if this as a product of Acorn, when in fact it started when Arthur Norman and Alan Mycroft wanted a C compiler to run ML/LCF and the ARchimedes was new. The compiler was written by them, and then taken up by Acorn. For some years we developed it together, but we recently agreed to separate and ARMremoved our copyright notice. We have built Norcroft C compilers for a wide range of processors, including many for japan with an arrangement with a japanese software company, but recently mainly startup chip manufactures.
The emphasis on Acorn/ARM is strange to me, as it also formed the basis on the Transputer C compiler (via Perihelion Software Ltd), a Hitachi mainframe C, as well as other architectures (sorry if the signature comes out wrong) ~~ jpff 18:07, 23 October 2011 (UTC) ]
This article is rated Stub-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||
|
There's a reference to "re-source the Norcroft back end" in Tom Crick's 'A GCC Front End for BCPL', which may be worth including. -- Trevj ( talk) 14:35, 16 June 2011 (UTC)
The currently stated site is the most appropriate one I know of. Perhaps there's something more obvious which I've missed. It's not listed there for WP:SPAM puropses, despite such an appearance from the URL. I hope this makes sense. Thanks. -- Trevj ( talk) 22:52, 16 June 2011 (UTC)
This guide published by Castle Technology states it is "Based on a two part article which appeared in both Archive and Acorn User, November/December 2002." Therefore, if anyone reading this has access to the relevant publications it could be useful. I don't know whether they include any extra information, or if it's all in that doc. In any case, Archive and Acorn User would be preferable in terms of reliable sources. -- Trevj ( talk) 13:03, 17 August 2011 (UTC)
Most of which can be seen by just visiting Codemist's website. Norcroft was a licencable C front end developed at the university of Cambridge (and later also at the university of Bath) used in teaching, and Acorn licenced it. It targets many many architectures. The history and architectures sections of this article are completely made up. And many elements in the main section (including ownership etc) are misleading. Also, useful information such as the fact that ARM themselves abandoned the Norcroft frontend for EDG's are missing. Sort it out, guys. — Preceding unsigned comment added by 82.6.165.102 ( talk) 15:53, 20 October 2011 (UTC)
I'm confused. http://www.codemist.co.uk/ncc/index.html says Acorn Computers ARM C Compiler. This is the original ANSI C compiler known as Norcroft C. But that page is titled Codemist Compilers / Norcroft, which implies that all the other compilers (listed beneath Acorn on that page) also fall under the Norcroft title. (Which is ambiguous, if "Norcroft C" refers to the Acorn compiler.) Should there be subheadings within this article for each compiler? I've just emailed Codemist to request input (pointing to WP:COI and WP:V).
Additionally, I think that the 'History' and 'Uses' headings should be retained (perhaps as subheadings within 'Acorn C/C++'). Help:Section states A page can and should be divided into sections [...] Removing section headings could result in unstructured expansion of the article. While I can't find any policy as such, e.g. at MOS:HEAD, the purpose of sections is clearly to structure articles. WP:BODY also states Very short or very long sections and subsections in an article look cluttered and inhibit the flow of the prose. but (with the exception of the 'Architectures' seciton) I wouldn't consider them "very short". So where do we go from here? Thanks. -- Trevj ( talk) 07:49, 21 October 2011 (UTC)
First I should make it clear I am a director of Codemist Ltd who wrote the Norcrift C Compiler and still sell it (see http://codemist.co.ukncc). The main page seems to talk as if this as a product of Acorn, when in fact it started when Arthur Norman and Alan Mycroft wanted a C compiler to run ML/LCF and the ARchimedes was new. The compiler was written by them, and then taken up by Acorn. For some years we developed it together, but we recently agreed to separate and ARMremoved our copyright notice. We have built Norcroft C compilers for a wide range of processors, including many for japan with an arrangement with a japanese software company, but recently mainly startup chip manufactures.
The emphasis on Acorn/ARM is strange to me, as it also formed the basis on the Transputer C compiler (via Perihelion Software Ltd), a Hitachi mainframe C, as well as other architectures (sorry if the signature comes out wrong) ~~ jpff 18:07, 23 October 2011 (UTC) ]