Closed (fixed)
Project:
Grammar Parser
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
25 Feb 2010 at 22:01 UTC
Updated:
12 Mar 2010 at 18:30 UTC
I have noticed the following cases which I do not feel are desireable.
-// function testFieldFormMultiple() {
-// $this->field = $this->field_multiple;
-// $this->field_name = $this->field['field_name'];
-// $this->instance['field_name'] = $this->field_name;
-// field_create_field($this->field);
-// field_create_instance($this->instance);
-// }
+ // function testFieldFormMultiple() {
+ // $this->field = $this->field_multiple;
+ // $this->field_name = $this->field['field_name'];
+ // $this->instance['field_name'] = $this->field_name;
+ // field_create_field($this->field);
+ // field_create_instance($this->instance);
+ // }
- /**
+/**
* TODO:
* - Test field visibility
* - Test profile browsing
- if ($contact !== TRUE) { // If true then attempting to find error message.
+ if ($contact !== TRUE) {
+ // If true then attempting to find error message.
In order to make this work the most consistently and easiest I vote for treating the first two as the same case and fix the last one to leave comment on previous line.
The first two just need to leave whatever spacing existed in front of the comment. In fact you might just do that always...thus the { // case would be the same in that it is prefixed by " " and not "\n ".
Comments
Comment #1
boombatower commentedAfter discussion the other cases make sense, except that the comment on the if is not indented...and that preferably it should be placed on the preceding line.
Still looks like block comment formatting is messed up:
to
Should be left alone.
Comment #2
solotandem commentedFixed in next dev release.