Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
other
Priority:
Minor
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
10 Jul 2010 at 08:40 UTC
Updated:
3 Jan 2014 at 01:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
klonos+tag
Comment #2
EvanDonovan commentedIssues are fixed in the highest-numbered version of Drupal and then backported, if necessary.
Comment #3
klonosI agree on setting these to minor Evan. As for the version, I am testing on D6 setups and I am not sure the files are the same in their corresponding D7 'brothers' (or if their D7 versions even exist). How about we let another person with D7 setups report these D7 coding standards errors (if any)?
Comment #5
avpadernoThere are many files that uses , instead of ; let's see if the patch works.
Comment #6
klonos...lets have all D7 Coding standards issues here then.
Comment #7
avpadernoThe report would become a big mess. Let's use a single report for a single task.
Comment #8
klonosFixing coding standards is a single issue!
Please take a look at my reply here: #850170: The $string argument to t() should not begin or end with a space.
Comment #9
avpadernoIf you are going to provide a single patch for all the parts that do not respect the coding standards, then it would be fine. Until you don't provide such patch, please leave the title as it is now.
Comment #10
aspilicious commentedDon't use one patch to fix all these issues. Do it in smaller patches.
This one is fine.
Comment #11
tstoecklerMaybe since we're already touching those lines we could fix the spacing issues here. There are other spacing issues in this file and I wouldn't want to scope creep that into this patch, but it feels wrong to see such a line with a '+' in front of it.
Either way, this patch is RTBC. I explicitly checked that there are no code changes involved other than 'else if' -> 'elseif' and since the tests pass, this is good to go.
Powered by Dreditor.
Comment #12
dries commentedCommitted to CVS HEAD. Thanks.
Comment #13
sunFriends, watch out. You changed the Archive_Tar class here, which does not follow Drupal's coding standards at all, because it's an externally developed library.
I recommend to revert these changes, and, discuss in a separate issue whether we want to change foreign library files like system.tar.inc (but then do it completely, e.g., start by running coder_format on it), or whether we want to keep such files as unaltered as possible for easier comparison with the original code and future updating. And link to that issue here.
Powered by Dreditor.
Comment #14
klonosGood point Daniel, but I cannot express any opinion regarding this.
Comment #15
avpadernoI agree that we should not change the content of the system.tar.inc file as it contains an external library; I thought it was a modified version adapted for Drupal.
To which revision should the file be reverted? As far as I can see, the file has already had many changes, since it has been added in Drupal repository.
I can provide a patch to restore the file as it was in revision 1.6. Is that enough, or should not we restore the file as it was on revision 1.2?
Comment #16
avpadernoThe attached patch reverts the code to revision 1.6.
Comment #17
avpadernoThis patch reverts the code to revision 1.2, which is the one without any of the changes done to the library when it has been added to Drupal repository. There is actually a change, but it doesn't aim to fix the code format.
Comment #18
sunThanks! Hope you agree, since this was not the only cosmetic change, let's move the entire discussion and reversion into #870204: Revert coding style changes to system.tar.inc & other externally developed files