Jump to content

Template talk:Infobox programming language

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Q2f96k1z09tsny5iva29 (talk | contribs) at 15:29, 2 August 2021 (→Semi-protected edit request on 2 August 2021: not done). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
WikiProject iconInfoboxes
WikiProject iconThis template is within the scope of WikiProject Infoboxes, a collaborative effort to improve the coverage of Infoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes
WikiProject iconComputer science Template‑class
WikiProject iconThis template is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer scienceWikipedia:WikiProject Computer scienceTemplate:WikiProject Computer scienceComputer science
TemplateThis template does not require a rating on Wikipedia's content assessment scale.
Things you can help WikiProject Computer science with:

Similar/Alternative languages

I think there should be a "Similar/alternative languages" item in this infobox. How do I make that happen? -Barry- 03:57, 29 April 2006 (UTC)[reply]

Someone in IRC just told me I should edit this page. If that's all that's needed to use the added item in another article, it should be mentioned that this article isn't just documentation on how to use the infobox. It actually allows you to change how the template works in the article. -Barry- 04:14, 29 April 2006 (UTC)[reply]
Didn't work. Still need to know how to change the template. -Barry- 04:24, 29 April 2006 (UTC)[reply]

Turing complete?

Is the "Turing complete" item really necessary? As the article on Turing completeness says, "Most programming languages, conventional and unconventional, are Turing-complete ... It is difficult to find examples of non-Turing complete languages". Are there any languages that have articles where the value of this item would be "no"? If not, isn't it somewhat superfluous? Oli Filth(talk|contribs) 08:36, 5 August 2008 (UTC)[reply]

Can we please lose the "turing complete" thing, per Oli Filth?! It's a silly and unnecessary distraction. The vast majority of PLs are Turing complete. It's definitely noteworthy in the articles of those few that are not, but Charity (programming language) or SQL-92 can note that fact in their leads. We don't use fields for topics where 99% of the uses share a value (let alone for a boolean value).... it would be like adding a field for "Text based": there are a few PLs that use icons rather than text, but not enough to change the box. Or probably even "Non-English keywords" is sufficiently rare not to get a field, as another example. LotLE×talk 21:05, 5 August 2008 (UTC)[reply]

'hello world' addition

Scheme
Paradigmfunctional

You know, I've noticed that most programming language articles include the basic 'hello world' construction for that language. it strikes me as a bit silly to have a separate section for that in these articles, and I'm thinking we should move them into the infobox. I'll add a parameter and post an example here, so you can see the effect. --Ludwigs2 16:54, 20 June 2010 (UTC)[reply]

Example added at right. --Ludwigs2 17:31, 20 June 2010 (UTC)[reply]

(A) Some Hello Worlds are so verbose they would bloat the infobox (I'm looking at you, Java!) (B) The Hello Worlds are often accompanied by explanatory prose, thus this field will either duplicate the code or will cause the example and its prose to become separated. --Cybercobra (talk) 00:44, 21 June 2010 (UTC)[reply]
Hello World examples are rarely this compact, and don't really fit the at-a-glance nature of infobox templates. There's nothing wrong with them being article boilerplate; the infobox doesn't need to cover everything that the article does. Conversely, the examples certainly should not be moved to the infobox, as infoboxes are only meant to be summaries and articles should stand alone fine without them. Chris Cunningham (not at work) - talk 11:43, 22 June 2010 (UTC)[reply]

"Programming language" label in a "programming language" infobox?

I assume this field is supposed to described the language used to implement another language, and not a field in which to put the name of the language being described. I changed the label of this field to "Implementation langauge" but left the field's name in the template the same. 75.186.5.185 (talk) 03:52, 8 December 2010 (UTC)[reply]

That filed doesn't make sense to me. A programming language doesn't have any implementation language, because it can (and usually does) have multiple implementations, written in various languages. Do you think this field makes sense or should it be removed? Svick (talk) 21:41, 8 December 2010 (UTC)[reply]
I personally think it's better to remove it and leave any descriptions of implementation languages in the article body. When you have multiple implementations with different languages used to implement each (think CPython vs Jython vs IronPython for example) trying to convey this in an infobox field would just look messy. Additionally, where I've seen the field already used -- in the entries for Rust, Scala, Haxe and OCaml -- the information provided is wrong anyway! Thanks. Hexene (talk) 18:20, 27 August 2013 (UTC)[reply]

TOBIE rank

I'd like to add TIOBE rank as one field of this template as I often find figures with Increase/Decrease/Steady of a company infobox quite informative. Here are the top 20 languages:

  1. Increase C
  2. Decrease Java
  3. Increase Objective-C
  4. Decrease C++
  5. Decrease C#
  6. Steady PHP
  7. Steady (Visual) Basic
  8. Steady Python
  9. Steady Perl
  10. Increase Ruby
  11. Decrease JavaScript
  12. Steady Delphi/Object Pascal
  13. Steady Lisp
  14. Increase Pascal
  15. Increase Visual Basic .NET
  16. Increase Ada
  17. Increase MATLAB
  18. Increase Lua
  19. Steady Assembly
  20. Decrease PL/SQL

I know that this might be as controversial as the use of Alexa rank in a website infobox, but I'd like to go ahead in a month or two unless there is a Oppose here. — Kennyluck (talk) 07:18, 2 January 2013 (UTC)[reply]

Year

Is there a definition of what is meant by the 'year' field? For example, Rust began as a single-person effort in 2006, had an official unveiling and public mailing list created in 2010, and made its first numbered release (0.1) in 2012, so which should it use? Thanks! Hexene (talk) 14:14, 22 June 2013 (UTC)[reply]

Template needs updating

Hi please remove label 12 and data 12 and merge them into data 11 please because test version and preview version are the same and please do some update to the stable release and preview release to reflect on a template change at template:LSR and template:LPR please. 86.135.252.13 (talk) 20:11, 25 March 2014 (UTC)[reply]

Not done: Hi. Are you sure you know what you are talking about? Best regards, Codename Lisa (talk) 01:59, 26 March 2014 (UTC)[reply]
hi yes because you have dublicate labels they both say preview release but on the data bit one says preview and the other says test. 86.135.252.13 (talk) 07:29, 26 March 2014 (UTC)[reply]
Look, when someone says "Are you sure you know what you are talking about?" he or she means "I cannot locate or verify what you are referring to. Please elucidate with line number, sample snippets of the code, etc." Label 12 is "Influenced by". Label 11 is "Dialects". Label 7 is "Preview release" which accepts its value through |latest preview version= and its aliases |latest test version=, |latest_preview_version= and |latest_test_version=. (Sorted by the order of precedence.)
Best regards,
Codename Lisa (talk) 22:26, 26 March 2014 (UTC)[reply]

Spacing

Can we come up with a way to add spacing around the logo/caption in C (programming language) without using hacks like multiple br tags? seems like if the spacing is that useful, we should add it to the infobox directly. Frietjes (talk) 14:04, 30 April 2014 (UTC)[reply]

Changing "appeared in" to "initial release"

Would there be any opposition to this? I ask because this phrasing is awkward when the exact date of release is known Sizeofint (talk) 03:27, 8 April 2015 (UTC)[reply]

Hi. Sometimes, this infobox is put an article about a language, not an IDE. So, there would be no initial release at all.
Best regards,
Codename Lisa (talk) 10:38, 8 April 2015 (UTC)[reply]
Thanks for responding. I'm really referring to OpenCL rather than any IDE. Wouldn't there have to be a date when the language was made public/widely available? I would think that even for a language like B it would make as much sense to say "initial release: 1969" as to say "appeared in: 1969". Sizeofint (talk) 16:57, 8 April 2015 (UTC)[reply]
I am not sure. "Languages" aren't "released". These two words don't collocate. Programming languages appear, are implemented and are adopted. And since at least I don't think "appeared in" is wrong, on the whole I think the change you suggest is somewhat of a downgrade. Best regards, Codename Lisa (talk) 09:22, 9 April 2015 (UTC)[reply]
Hmm... I guess I understand your reasoning. What about just dropping the "in" so the infobox will have "Appeared" and then a date? That would allow use of specific days without sounding awkward. Regards Sizeofint (talk) 19:53, 9 April 2015 (UTC)[reply]
You might be on to something there. We usually write "it appeared on 19 August 2019", "it appeared in August 2019", "it appeared in 2009", "it appeared in 2010s" but still I expect a lot of infoboxes would report day too. Or do they...? Maybe "first appearance"?
I don't know.
Best regards,
Codename Lisa (talk) 20:44, 9 April 2015 (UTC)[reply]
"First appearance" or "First appeared" sound pretty good to me. Most languages don't include the exact day at this point but that might be an effect of the current wording. I know for at least Go and OpenCL C the exact date is available. Sizeofint (talk) 20:56, 9 April 2015 (UTC)[reply]

|latest test version= and |latest test date= aliases no longer work

Ping @Codename Lisa: and @Waldir:, who else? I found the issue at Special:Diff/742033177. 80.221.159.67 (talk) 07:48, 1 October 2016 (UTC)[reply]

Thanks for the notice. The issue seems to have been introduced in Special:Diff/736291678, so I'll let Codename Lisa handle it. --Waldir talk 12:50, 1 October 2016 (UTC)[reply]
 Done Call me any time if you had more problems. —Best regards, Codename Lisa (talk) 13:41, 1 October 2016 (UTC)[reply]

Examples of scope

What's the purpose of scope? It will be useful to have some concrete examples. It's not very clear from the definition given. — Preceding unsigned comment added by Jsamwrites (talk • contribs) 11:49, 23 March 2017 (UTC)[reply]

Memory Management (04/2017)

A field for memory management usage type will be useful: garbage collector, counting references ...(04/2017)

Package managers

How about adding a parameter for specifying the package managers (official and unoffical) of the langauge? Galzigler (talk) 14:31, 27 May 2017 (UTC)[reply]

Introduced Constructs

I think it would be useful to add an optional introduced_constructs section to the infobox. For example,

appears in the article on Simula. It seems to me that this information would be both useful and compact enough to fit in the infobox.

Bhbuehler (talk) 03:57, 14 January 2019 (UTC)[reply]

Semi-protected edit request on 2 August 2021

I think we could add a |country_of_origin or |origin field to show where the language was developed. We already tell who developed or created it but not where they are from. We also show the country of origin of a lot of products and productions in other templates, so knowing where a programming language comes from might be relevant. 200.242.43.202 (talk) 15:21, 2 August 2021 (UTC) 200.242.43.202 (talk) 15:21, 2 August 2021 (UTC)[reply]

 Not done: I don't think that's information that would really ever be relevant for the infobox of a programming language. For a random example, the fact that Guido van Rossum is Dutch isn't even mentioned in the prose of Python (programming language). It could plausibly be mentioned in the history section, but a factoid like that I don't think is relevant enough for an infobox. Maybe others will disagree with me though. ‑‑Volteer1 (talk) 15:29, 2 August 2021 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Template_talk:Infobox_programming_language&oldid=1036764640"