18

I see no reason why it wouldn't be. Provided it is otherwise on topic. Which, your question is. The code works, you're honestly looking for a review, etc. What stops us from reviewing Fim++ is that we can't tell if fim++ code works, because there is no compiler implemented for the language. No compiler = hypothetical code. So, Fim++ remains off topic until ...


18

NO, it shouldn't exist, not even be a synonym! c# has major differences between versions, too. And yet, the only C# tag we have is c#. How do we address this? C# 2.0 introduced generics. Enter the generics tag. C# 3.0 introduced linq. Enter the linq tag. C# 4.0 introduced the Task Parallel Library. Enter the task-parallel-library tag. C# 5.0 introduced ...


16

The reason why these tags are useful is that they affect the set of helpful review comments. The way that I interpret these tags is: python + python-2.7 — only required to run under Python 2.7, presumably because it is interfacing with a legacy system that has not yet been ported to Python 3. Review comments about portability to Python 3 are probably ...


16

Of course these languages are allowed. We have users in our chat room who grew up programming on these systems, and while the assembly user base isn't as strong as others, it is large enough that you could likely get a review.


15

java-8 should not be a full tag, but a synonym to java. Reasons: People tagging with java-8 will also need to tag with java anyway. Questions with Java8 will always need some text 'disclaimer' anyway: I wrote the following code with help of some Java 8 Maybe I've gotten a bit over excited with the new options in Java 8 in a year or so, all Java ...


12

Absolutely! The newest cobol question was asked last April, and it's funny you bring up C64 basic just recently I was considering finding an emulator and implementing a tic-tac-toe game and putting it up for review on the main site. [...] they could be a pain for some reviewers. Sure. And they could be a challenge for some other adventurous reviewer that'...


11

No - these tags should go! I have been struggling to describe why I think these tags are bad. There are a number of arguments for, and against these tags. First though, some assumptions I have made (which may not be right) Assume we are focusing on language-specific implementations of common computer science concepts. For example, strings are common to ...


11

Yes, with a few exceptions. I'd say yes, as long as the question isn't actually asking for a review of code written in the language itself. If the question is asking for review of a Nothing compiler/interpreter, I'd say it's on-topic. There wouldn't be many variations of the compiler implementation though, and chances are I wouldn't vote up a question ...


10

Deprecated functions are not a new thing, and not a thing solely to swift. You don't need to edit every question to replace println, you simply need to understand those questions/answers contain old code. Python went and changed from print statement to print(statement), and the existing questions weren't edited. Granted that the changes from Python 2.7 to 3 ...


10

Sure. We have plenty of lua questions. I don't see any reason why a Lua question using the ROBLOX API would inherently be off-topic. Just follow the standard How to Ask guidelines.


10

I think another question to ask is: Do we want to review lolcode? Also related is, do we hate or like 'fun'? My opinion is that, as long as lolcode does not become as popular as python or other popular languages, one lolcode question every now and then is fine. I do however feel that lolcode in general is very similar to c-like languages, but with a ...


10

If I know all versions of Python, the easiest way for me to look at all of the Python questions isn't for me to come up with some complicated search that makes sure I'm including all the possible Python tags. The easiest way is for all of the Python questions to have the python tag. The version specific tag (python-2.7) just provides the additional detail ...


9

Swift can be used to develop for osx, ios, windows, linux, and possibly more platforms, since it is open source. Rather than "forcing" one OS that you develop for, we should leave it to the asker to decide on which OS he decides.


8

I don't see why not. We allow questions on languages like makefile and bash, and Dockerfiles wouldn't be that different. Be sure to include contextual information about what the container is intended to be used for, and how it might fit with other containers you might have.


8

Yes, but... If you want a review on the code written on the Nothing language, that would be off-topic since the "code" is ... well, nothing! And this would conflict with this section, on the on-topicness (emphasis mine): Make sure you include your code in your question This site is for code reviews, which are hard to do when the code is behind a ...


8

If there are major and possibly non-backwards compatible differences between a new version of a language and its previous versions, then I think we should keep the tag. For example, lets look at C++. Bjarne Stroustrup said that C++11 feels like a new language. I personally have found the c++11 tag to be useful. My answers can sometimes vary depending on ...


7

That's a really old problem. I often look for a version tag when I want to answer questions, be it with C++ or Python because I sometimes don't feel like answering questions for some versions, but I also sometimes want to see all the latest questions for the language, whatever the version. So I like having both the general and the version-specific tags on ...


7

Is it reviewable? Sure. Should we review? I guess, if someone feels so inclined--but why? But for me, there's not much point to it. It's truly a toy-language. No one will ever write any serious production code out of it. Moreover, the example questions we have of it show that the language itself encourage ridiculously named variables. Consider, the ...


6

Yes? Why not? I mean, we did so, didn't we?


6

I think that the java-8 tag should stay until Java 8 gets officially released, it seems to be the way over at Stack Overflow. The argument to do it like this is that people using Java currently are not expecting any Java 8 code, and in the future we ought to be able to expect from them that they are to expect Java 8 answers, unless specifically indicated ...


6

The language syntax highlighting used in Code Review (normally) comes from the language tag set on the post. This is one of the reasons we have only one language tag per post. The language syntax highlighting is done through a prettify script that is used in all code-related Stack Exchange sites. The "definitive" guide is here: What is syntax highlighting ...


5

Glancing at the front page of questions tells me that you're exaggerating a bit. Not every python question has a related version tag. Either way, burnination isn't the right course of action here. Synonyms would be much more appropriate. Personally, I don't see a need for version tags. I mean, we don't have c#1, c#1.2, c#2, etc. If a specific version of ...


5

How to tag Inno Setup questions ? What I'm missing in the question you linked is the inno-setup tag. That's the major tag there, because even if Inno Setup installer uses Pascal Script as a scripting engine, we can talk about it as a separate "language". So that's what I would add except pascal-script to that question (notice the - char I used because if we ...


4

The answer is: It depends. Honestly, I don't see how swift should be considered special here at all. It's certainly not any different from objective-c. And the only thing that perhaps separates these languages from other languages is that when you're writing code in these two languages, you're usually writing for a specific operating system (like you're ...


4

If we look at the progression of the language that is used for texting and the fact that more and more internet browsing happens from mobile devices, who is to say that LOLCODE won't become the next Mobile App Development language? Eventually people will see this as a sub-language set of English used specifically for communicating over mobile devices. I ...


3

The entire JavaScript ecosystem is a mess, because you have languages built on-top of other languages, with subsets of those languages it's a mess. As we know JavaScript is a language, but it is also a subset of the ECMAScript language specification. ECMAScript also has other compliant languages, such as ActionScript and JScript. ECMAScript also has a ...


3

SO has pascal, delphi, and pascalscript (note, no - in pascalscript). SO also has object-pascal which indicates it is a super-set of free-pascal and delphi My 'research' indicates that the three are treated distinctly in different places, and should be treated distinctly here. I vote, what we have is fine. The concepts are distinct enough to group the ...


2

Having both python and python-2.7 doesn't supply more information than just python-2.7 on it's own. If backwards compatibility is required (it usually isn't), apply both python3 and python-2.7. However, this is along the lines of using both c++ and c on the same question. They are different languages, don't use both tags at the same time. We don't have a c-...


Only top voted, non community-wiki answers of a minimum length are eligible