Hi,
Ingo wrote:
> But look at the actual C++ we are talking about here. There are
> neither templates nor rocket science in there.
Yes, it's nowhere near as bad as modern C++.
> That can be combined with writing unit tests if one feels so inclined,
> which is another desideratum.
Ingo, have
On Wed, Sep 10, 2014 at 09:57:31AM +0100, Ralph Corderoy wrote:
> Hi,
>
...
>
> That's my favourite. Its conventions might be different, given its age,
> but I think it's pretty consistent. Enthusiasm for anything other than
> trivial changes in style would soon wear thin if bugs were being
>
> you may be right about setter()/getter() usage;
He is definitely right! :-)
> other modifications would really improve readability and
> maintainability:
> - capitalization of class names
> - a naming convention for class member variables
Mhmm, this is much work, and I don't s
On Wed, Sep 10, 2014 at 12:16:06PM +0200, Werner LEMBERG wrote:
>
> > you may be right about setter()/getter() usage;
>
> He is definitely right! :-)
>
> > other modifications would really improve readability and
> > maintainability:
> > - capitalization of class names
> > - a na
>> Additionally, `git blame' would become much more inconvenient to
>> use.
>
> I am not familiar with git and git blame, used cvs in my active
> time. Could you explain, what the problem with upper case class
> names and git blame would be?
Please say `git help blame' on the command line and r
Hi,
Werner wrote:
> Please say `git help blame' on the command line and read this
> command's manpage :-)
Also http://git-scm.com/docs/git-blame
> > git grep color_flag
http://git-scm.com/docs/git-grep
And the -w option is handy, just as with grep(1), to avoid matching
tricolor_flag and color
Werner LEMBERG wrote:
|Please say `git help blame' on the command line and read this
|command's manpage :-)
Or "$ man git-XY", e.g., "man git-blame" (but Ralph yet said so).
|>>> - reducing the number of global variables
|>>
|>> Why? Again, please provide an example that could ben
> Because it consumes space in BSS, or DATA -- and then even causing
> linker work upon loading time, even if never used.
> A program with a DATA section is shit ;)
Well, I don't care :-) groff uses static constructors to initialize
some of the global variables, this is a very nice and elegant fe
Hi Ulrich,
Ulrich Lauther wrote on Wed, Sep 10, 2014 at 01:01:37PM +0200:
> On Wed, Sep 10, 2014 at 12:16:06PM +0200, Werner LEMBERG wrote:
>> Additionally, `git blame' would become much more inconvenient to use.
> I am not familiar with git and git blame, used cvs in my active time.
> Could yo
Werner LEMBERG wrote:
|> Because it consumes space in BSS, or DATA -- and then even causing
|> linker work upon loading time, even if never used.
|> A program with a DATA section is shit ;)
|
|Well, I don't care :-) groff uses static constructors to initialize
|some of the global variables,
On Wed, Sep 10, 2014 at 03:55:12PM +0200, Werner LEMBERG wrote:
>
> > Because it consumes space in BSS, or DATA -- and then even causing
> > linker work upon loading time, even if never used.
> > A program with a DATA section is shit ;)
>
> Well, I don't care :-) groff uses static constructors to
On Wed, Sep 10, 2014 at 05:29:13PM +0200, Ingo Schwarze wrote:
> Hi Ulrich,
>
> Ulrich Lauther wrote on Wed, Sep 10, 2014 at 01:01:37PM +0200:
> > On Wed, Sep 10, 2014 at 12:16:06PM +0200, Werner LEMBERG wrote:
>
> >> Additionally, `git blame' would become much more inconvenient to use.
>
> > I
On Wed, Sep 10, 2014 at 01:23:41PM +0200, Werner LEMBERG wrote:
>
> >> Additionally, `git blame' would become much more inconvenient to
> >> use.
> >
> > I am not familiar with git and git blame, used cvs in my active
> > time. Could you explain, what the problem with upper case class
> > names
> The problem with global variables is their long range effect,
> comparable with the infamous goto statement: considered harmful.
I like `goto' a lot, and it is an invaluable instruction if used with
care. The same is true with global variables. Sorry to say, but we
are now going into hearsay
> well, I know how to find and read man-pages. But I was confused
> about the connection you made between moving to upper case class
> names and git blame. I guess, what you really wanted to say is that
> ANY nonfunctional change would lead to "false reports" of git blame.
Exactly. You have to
On Wed, Sep 10, 2014 at 08:02:30PM +0200, Werner LEMBERG wrote:
>
> > The problem with global variables is their long range effect,
> > comparable with the infamous goto statement: considered harmful.
>
> I like `goto' a lot, and it is an invaluable instruction if used with
> care.
Yes, e.g., for
Hi Ulrich,
> The problem with global variables is their long range effect,
> comparable with the infamous goto statement: considered harmful.
I see little difference between looking at all the locations where the
global is changed and doing the same but for calls to a `set' routine,
other than th
On Wed, 10 Sep 2014, Werner LEMBERG wrote:
The problem with global variables is their long range effect,
comparable with the infamous goto statement: considered harmful.
I like `goto' a lot, and it is an invaluable instruction if used with
care. The same is true with global variables. Sorr
Ingo --
On Wed, Sep 10, 2014, Ingo Schwarze wrote:
> Some things work more or less similarly in git:
>
> * cvs co module -> git clone module
>Except that it also mirrors the whole repo including history.
...
Your table is great. I'm going to print off a copy. It was a lot
of typing, s
> I may have to look into this C++ stuff. I have only written C and I
> have not figured out how to write multi-threaded applications
> without global variables. And I make good use of goto and
> longjmp. Apps would be a lot junkier without them.
Well, right now groff's C++ is essentially C code
Ingo --
On Wed, Sep 10, 2014, Ingo Schwarze wrote:
> > One of the issues he raised with me off-list is an apparent lack
> > of organization. It's true.
>
> I disagree. Lack of reviewable patches is not lack of organization.
> If you have reviewable patches and people go for each other's throat
On Wed, Sep 10, 2014 at 10:16:47PM +0200, Werner LEMBERG wrote:
>
> > I may have to look into this C++ stuff. I have only written C and I
> > have not figured out how to write multi-threaded applications
> > without global variables. And I make good use of goto and
> > longjmp. Apps would be a lot
Feel free to use inside the groff project in any way you like,
including republishing and including in official lists,
but please don't change the content without speaking to me.
Bernd Warken:
Projects/components
- author of `g
Hi groff list,
As I mentioned to Werner, I'm a professional software engineer, regular groff
user, and Unix tool enthusiast, and I'd like to contribute back to groff
development. I'm most interested in working on grohtml. I'd like to start
with something simple, like a bug fix or a refactorin
24 matches
Mail list logo
