comments

I published my Android app to Google Play and everything was fine. I got about 5000 user reviews with an average 4.6 mark. But at some moment I started getting lowest mark with an insane speed. Several hundred 1 marks during 5 days. So my rating fell to 4.3. There were no complains from users, no comments, just a huge number of lowest marks. I suspect these were fake reviews. Probably paid by competitors. Is there any way to identify that? To prevent that? Does Google protect us from fake reviews in any way? I think the best thing to do is contact Google and make them aware of the issue. There

I have never, ever, seen a PHP file using hashes ( # ) for commenting. But today I realized that I actually can! I'm assuming there's a reason why everybody uses // instead though, so here I am. Is there any reason, aside from personal preference, to use // rather than # for comments? Aziz The answer to the question Is there any difference between using "#" and "//" for single-line comments in PHP? is no . There is no difference. By looking at the parsing part of PHP source code, both "#" and "//" are handled by the same code and therefore have the exact same behavior. PHP's documentation

So far as I understand it, messages are associated with commits. But when you look at a repo on GitHub it helpfully lists the message by each file, for when it was last changed. I'd like to replicate that in a web view of a repo I have. Looking at the GitHub api it looks to me the only way to get that info is to download all the commits (which can be paged), and work from the most recent ones assigning commit messages to the files in your local cache, going further and further back until you've got the message for every file, potentially to the very first commit, if any of the files have not

How do I comment multiple lines in Clojure? Actually, there is a way! (comment (defn hey [] ("Hey there!")) Check me out! ) Just wrap your comments in (comment ..) :) Have fun! Clojure supports a #_ reader macro which completely skips the next form. This is mentioned on the page about the Clojure Reader . There is also the comment macro which has a similar effect, but is implemented differently. Both the above require that the thing that you're commenting out is otherwise a syntactically correct S-expression. Some Lisp dialects have a multi-line comment that can contain arbitrary text, but I

Would just like too see what peoples Stored Procedure/Function etc comment headers look like (so post your examples)...I've only really seen what the SQL Server Management Studio creates but am interested in what other peoples look like...the formatting, characters used, procedure information/details etc I guess are what really makes them different... SQL Server Management Studio (version 9) stored procedure comment header default: -- ============================================= -- Author: Name -- Create date: -- Description: -- ============================================= /*****************

This question already has an answer here: How Do I Document Packages in Java? 3 answers I am using CheckStyle , FindBugs , and PMD to validate my Java code. I have fixed almost all the bugs caught by these tools. I am not able to understand how to write "package comment" which is a bug caught by checkstyle. I have gone through the documentation of CheckStyle, but I don't understand it. Could someone help me in writing a package level comment in Java? Michael Borgwardt Package-level javadoc comments are placed in a file named package-info.java inside the package directory. It contains the

Looking down this build.gradle file apply plugin: 'com.android.application' android { compileSdkVersion 21 buildToolsVersion "21.1.2" defaultConfig { applicationId "package.myapp" minSdkVersion 19 targetSdkVersion 21 versionCode 1 versionName "1.0" } buildTypes { release { minifyEnabled false proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro' } } } dependencies { compile fileTree(dir: 'libs', include: ['*.jar']) compile 'com.nineoldandroids:library:2.4.0' } What if I would like to write a comment on why did I chose this library for this project , what is the

I have started to use the FIXME , TODO , ??? and !!! tags in XCode but have am finding it painful that it does not recognise the tags when they are within a function. The tags are only recognised outside a given function. How can I get these tags recognised within a function (as this is where the bugs are)? Florian Edited 2016-02-02 Xcode now supports //MARK:, //TODO: and //FIXME: landmarks to annotate your code and lists them in the jump bar. To find those special markups (and actually any markups you specify yourself), you can use the search navigator, enter the following string and then

I am developing a web application that can support threaded comments. I need the ability to rearrange the comments based on the number of votes received. (Identical to how threaded comments work in reddit ) I would love to hear the inputs from the SO community on how to do it. How should I design the comments table? Here is the structure I am using now: Comment id parent_post parent_comment author points What changes should be done to this structure? How should I get the details from this table to display them in the correct manner? (Implementation in any language is welcome. I just want to

Just a quick question: I've seen that some PHP functions are commented at the top, using a format that is unknown to me: /** * * Convert an object to an array * * @param object $object The object to convert * @return array * */ My IDE gives me a dropdown selection for the things such as @param and @return, so it must be documented somewhere. I've tried searching google but it won't include the @ symbol in its search. What is this format of commenting and where can I find some information on it? That's phpDoc syntax. Read more here: phpDocumentor Waqar Alamgir Functions: /** * Does something