shlomif/Perl-Devel-Trepan — comment on commit 6f49cae0f4a8fe8150b782c163241dcacc130135
File:  line 0
By rocky:

Is this so hard to read?

```perl
$x = 1; $y = 2; $z = 3;
```

that you go around splitting this on several lines? And if it is

```perl
$x = $y = $z = 0;
```

do you write that as:

```perl
$x =
$y =
$z = 0;
```
? Or split this into 3 separate assignment statements?

Do you try to line up the = sign in:

```perl
$first = 1;
$second = 2;
$third = 3;
```
?

because this is easier to read? I guess part of the point I am trying to make is that I doubt that just putting stuff on more lines in of itself makes things readable.

The thing about style is it is largely a matter of what one is used to. At one time I preferred indentation to be two spaces because again it is the minimum amount that gets the point across clearly. In some programming languages folks want 2 spaces, in some 4, and in some something different. After a while, I found I could just get used to any. So although I could get used to the multiple line thing, I think it silly and sad I can't write in the way I find the most logical and suits me the best.

When I say boilerplate, part of what I mean is that this stuff is uninteresting. Uninteresting to the point that if you totally skipped those lines and never read them, it wouldn't impact one iota the *essentials* of the program - the organization of classes, the algorithms, the fundamentals of what this program does and so on.

I know how to elide blocks of code, and I don't see a need to customize my Editor to elide this stuff. I want to write code in this way. The fact that you haven't seen it doesn't in of itself mean that this is a bad thing to do. Try it and live with it for a bit. If after trying it you can elucidate why it is so hard to read and why it is so important for you to be able read this, then let's discuss.

Also sad to me is that were spending this amount of time over things like this rather than:

* adding watchpoints
* adding out-of-process debugging
* adding signal handlers like gdb's "handle" command
* figuring out how to remove the globalness of the debugger to allow say profiing and debugging to be totally independent
* finishing and removing some of the weirdnesses of tab ReadLine completion

These to me are the more important issues.