Option "RemoveExpressionReturns" of JCF changed to False itself

[scarscc]

Dear all,

I found the option of JCF RemoveExpressionReturns often changes itself to False, although I set to true.

Is it a bug?

[Thaddy]

Afaik jcf is not maintained here but by JEDI unless it is forked.
jcf itself is one big bug regarding FPC syntax.
E.g. it chokes on many FPC only features, like the way objfpc mode declares and uses generics. And many more. JCF damages your code more often than it helps you.

[marcov]

Afaik jcf is not maintained here but by JEDI unless it is forked.

You mean like components/jcf2 in the lazarus sources?

[Thaddy]

the not accepting half the syntax one? 
Then again, my beloved ptop is also in need of a thorough update.
I am not interested in doing that because:
- tab is mapped to two spaces, not #9
- I format when I write. Is that old fashioned?

[scarscc]

Afaik jcf is not maintained here but by JEDI unless it is forked.
jcf itself is one big bug regarding FPC syntax.
E.g. it chokes on many FPC only features, like the way objfpc mode declares and uses generics. And many more. JCF damages your code more often than it helps you.

So do you have some recommendations to format code?

[marcov]

I do it pretty much like Thaddy, format when I write, and occasionally during refactor.   I don't use automated tools.

[Thaddy]

I do it pretty much like Thaddy, format when I write, and occasionally during refactor.   I don't use automated tools.

Makes us old fashioned...

wait....or not...

Try Python!
Does not allow formatting mistakes.
My recommendation is two spaces as indent/unindent for every block.
It is usually enough to write a tab stripper that replaces every #9 with #32#32

Most editors, including the Lazarus IDE allow you to configure that.

Tabs are evil, except on a real typewriter.

Alternatively in the console IDE:
ctrl-K I   //indent
ctrl-K U  //unindent
(wordstar syntax, the Lazarus IDE does not support that AFAIK, most other editors do)

[cdbc]

Hi

(wordstar syntax, the Lazarus IDE does not support that AFAIK, most other editors do)

Hmmm... Both my lazarus' do support that and Ctrl + I/U too...
Laz 3.6 & laz 3.3.1 (trunk)
Regards Benny

[Thaddy]

Did not ever use that.
Tnx for the info Benny

[DomingoGP]

Jcf2 package mantainer here  .

I found the option of JCF RemoveExpressionReturns often changes itself to False, although I set to true.
Is it a bug?

This happens when you set.

"Break lines that are longer than max line lenght" to "never"

So, it's not a bug, it is a consistency check.

Afaik jcf is not maintained here but by JEDI unless it is forked.

The lazarus fork ot JCF is maintained by Me, see commits in components/jcf2.

jcf itself is one big bug regarding FPC syntax.
E.g. it chokes on many FPC only features, like the way objfpc mode declares and uses generics. And many more. JCF damages your code more often than it helps you.

This is your opinion, and a few years ago it was correct but I honestly believe that with de changes made to the Lazarus fork in the last few years this is no longer true.

The Lazarus fork currently supports all the syntax accepted by the trunk version of FPC and some Delphi only syntax like long constants strings and inline vars.

I would encourage You to try the latest version of Lazarus and if You find any problems with JCF fill a bug report so we can try to fix it.

Regards

Domingo.

[Thaddy]

I respect your efforts, but there are severe issues, mainly regarding generics.
So keep up the good work.

[bytebites]

Afaik jcf is not maintained here but by JEDI unless it is forked.
jcf itself is one big bug regarding FPC syntax.
E.g. it chokes on many FPC only features, like the way objfpc mode declares and uses generics. And many more. JCF damages your code more often than it helps you.

Oh, so silly post from a senior member.