[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 105396] keep one-line blocks option does nothing
From:       "Steven T.Hatton" <hattons () globalsymmetry ! com>
Date:       2005-05-28 2:22:56
Message-ID: 20050528022256.7617.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=105396         




------- Additional Comments From hattons globalsymmetry com  2005-05-28 04:22 -------
Please don't underestimate the impact of this this type of feature on the 
user.  In the not too distant past, I procalimed I would never use oneline 
blocks in my code.  My opinion changed when I wrote several hundred lines of 
glue code that looks like this:

  inline osg::Vec2f vec2f(const a2f_T& v) { return osg::Vec2f(v[0], v[1]); }
  inline osg::Vec3f vec3f(const a3f_T& v) { return osg::Vec3f(v[0], v[1], 
v[2]); }

  inline osg::Vec3f vec3fX(a3f_T a) { return vec3f(a3fX(a)); }
  inline osg::Vec3f vec3fY(a3f_T a) { return vec3f(a3fY(a)); }
  inline osg::Vec3f vec3fZ(a3f_T a) { return vec3f(a3fZ(a)); }

  inline osg::Vec3f vec3fXY(a3f_T a) { return vec3f(a3fXY(a)); }
  inline osg::Vec3f vec3fYZ(a3f_T a) { return vec3f(a3fYZ(a)); }
  inline osg::Vec3f vec3fXZ(a3f_T a) { return vec3f(a3fXZ(a)); }

  inline osg::Vec3f vec3fX(osg::Vec3f v) { return vec3fX(a3f(v)); }
  inline osg::Vec3f vec3fY(osg::Vec3f v) { return vec3fY(a3f(v)); }
  inline osg::Vec3f vec3fZ(osg::Vec3f v) { return vec3fZ(a3f(v)); }

  inline osg::Vec3f vec3fXY(osg::Vec3f v) { return vec3fXY(a3f(v)); }
  inline osg::Vec3f vec3fYZ(osg::Vec3f v) { return vec3fYZ(a3f(v)); }
  inline osg::Vec3f vec3fXZ(osg::Vec3f v) { return vec3fXZ(a3f(v)); }

I depend on automatic formatting to keep track of syntax determined 
indentation.  That is one of the most essential features an IDE can offer to 
me.  If I open the above code in KDevelop and apply the reformat source 
command, 100 loc becomes 400 loc.  What fit one one screen, now requires a 
lot of scrolling.  If I save the code after reformatting it, then open it in 
Emacs, where I created it, I have no way of getting it back to the form I had 
short of writing some Lisp to rereformat the code, or spend a few minutes 
pounding on the keyboard.

Much of what I would like to see in the KDevelop regarding source formatting 
is in the perview of AStyle, and I will take it to the AStyle developers.  If 
KDevelop's AStyle integration is broken, I cannot determin what feature are 
actually missing.

I'll have a look at the KDevelop code and try to determin where exactly the 
breakage is, and point it out so that a person qualified to fix it can easily 
address the problem. But I have to admit, determining the entry points into 
KDevelp is quite a challenge for me.
[prev in list] [next in list] [prev in thread] [next in thread]