Re: [ jEdit-devel ] jEdit coding style

[Shlomy R. <sre...@gm...>]

I believe Slava used to add folding markers around every method. If there
are methods without them, I guess these methods were not created by Slava
and the developer who added them didn't know about the explicit fold markers
or just forgot to to add them. Note also that an important detail of these
markers is that the first line contains the method name (or something that
describes the content of the folds, e.g. "private members"), so if all
methods are folded, you can still see the names.

However, I see this convention as a thing of the past. Nowadays, do you
search for something in a file by scrolling the file, or do you perform a
Search (Ctrl+F) or use SideKick (or some tag jumping feature)? In my
opinion, when a file contains many methods, the markers are almost useless
and just add overhead (time to create them, larger size on disk, more
scrolling, more search results...).

Shlomy

On Wed, Jul 14, 2010 at 4:56 PM, Dale Anson <da...@gr...> wrote:

> Alan, thanks for the pointer to the eclipse formatting file.  I see it
> agrees with Shlomy, spaces are added after "if", "while", etc.  I think I'll
> just handle the brackets and indenting and not worry about the rest.
>
> I still wonder about the folding markers -- should they be inserted around
> each method?  I see some files have quite a few methods without any, and
> other files have them around not only methods but whole sections of methods.
>  Since I don't use folding myself, I don't care one way or the other, but I
> thought it would be useful to have the plugin insert the markers as
> necessary.
>
> Thanks,
>
> Dale
>
>
> On Tue, Jul 13, 2010 at 9:46 PM, Shlomy Reinstein <sre...@gm...>wrote:
>
>> Since Slava no longer works on jEdit, I don't think the style he set at
>> the time should be followed, unless the current team of developers would
>> like to keep it. If we don't have this in a document in SVN, we should
>> probably decide on a convention and write it in a document that will be in
>> SVN.
>> I dislike the first convention (no space after "if", "for" etc) very much,
>> and have never followed that convention. (Also, I never heard of it as far
>> as I remember...)
>>
>> Shlomy
>>
>> On Wed, Jul 14, 2010 at 12:51 AM, Dale Anson <da...@gr...> wrote:
>>
>>> I'm looking for some details on the coding style used in jEdit source
>>> code.  I recall that Slava sent an email or two with some details, but I'm
>>> not sure I've found them all.  What I have so far:
>>>
>>> - no space after if/where/...  (any idea what else falls under the ...?
>>> for and catch?)
>>> - brackets on separate lines
>>> - 8 space indents without soft tabs
>>>
>>> Any idea about the rules for the folding markers, //{{{ and //}}}?
>>>
>>> I'm adding some configurations to the Beauty plugin for Java code, and
>>> wanted to include this coding style as an option.
>>>
>>> Thanks,
>>>
>>> Dale
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by Sprint
>>> What will you do first with EVO, the first 4G phone?
>>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>>> --
>>> -----------------------------------------------
>>> jEdit Developers' List
>>> jEd...@li...
>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>
>>>
>>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>