The ever re-appearing /= question.

[Thaddy]

I know, Marco, but still it is a fix, not a feature. We both were there before 2000 and probably did not pay attention. As a user, at that point in time, I was not critical enough, I confess.

[marcov]

I know, Marco, but still it is a fix, not a feature. We both were there before 2000 and probably did not pay attention. As a user, at that point in time, I was not critical enough, I confess.

It was not there, now it is. Sounds like a feature to me.

[Thaddy]

@Marcov

How? What was there was a bug, now it is fixed. (It was a breach of contract)
Whoever wrote it (Daniel, maybe?) probably intended to write the feature in full. This is still not the case, hence my insistance. This is rather assumptious, I know.

Otherwise all bug fixes are features, did you think about that when you wrote that? (Although that would be "Delphi compatible"  )

[PascalDragon]

I feel very strongly about this and need your support to get this applied:

You can gather all the support you want. The answer is and stays no.

I suggest that {$coperators on} are deprecated in upcoming FPC 4.0.

While I am very tempted to do just that or at least to throw out the -Sc from the default fpc.cfg marcov is also right that this is not very realistic. Keeping them in does however not mean that we'll extend them in any way. They should not have been added in the first place and also shouldn't have been added to the default fpc.cfg.

[Thaddy]

@PascalDragon

Frankly I agree with you as you know: but the patch is a bug-fix for something we both did not want and you can't remove it, so why don't fix it? The patch is sound, well tested and has no impact apart from fixing the behavior to be compatible with the contract that it behaves like C.

Meaning I take no for an answer as in the feature should not be there, but I refuse to take it as a bug fix. That is incoherent.
It is a FIX, not a feature. At least try the patch yourself.

Why would you leave in malfunctioning code?
Either remove it (you have my vote!) or apply the fix.

Anyway, I feel that only a substantial bribe over a sumptuous dinner with many others of the core team present would help convince you? 

But really, this is just emotion over technical merit and you are usually so precise (as I am about the fix, no noticeable incoherence this time  ) in such matters.

[440bx]

I feel the same way as @dbannon on this one.  Repurposing "/" to mean division for both integers and floats only creates confusion, incompleteness and possible ambiguities because then "div" is superfluous and "/" becomes ambiguous because it is associated with both integers and floats.

That's just a mess.  I wouldn't touch that one with a 10 foot pole.

C operators are already a mostly unwelcome feature in the language, adding a black sheep to that family is not a good idea.

Best thing is to leave the thing alone.  Cut your losses, live and learn.

[Thaddy]

It is an unwelcome feature just like inline var, but the design promise is that the {$coperators} work like, surprise..... C!!!! That is the design, but half-implemented in the case of the compound division /=. This is not a feature but a fix for something many of us did not want in the first place.
I might add that the issue was also controversial in C for the same reasons:
You could not write int /=float for many decades because it means the explicit truncation and you had to truncate in normal C notation.
Just like I did: int/float is trunc(int / float).
This is not merely semantics: if you promise that for the purpose of translating C code to Pascal the compiler accepts C style operators, at least make sure they work. I am not asking for new extended C operator features, I am asking to fix an existing one, nothing more, and I did so.

I am waiting for the next episode of ..... Soap.
https://www.youtube.com/results?search_query=confused+you+will+be+after+the+next+episode+of+soap

[MarkMLl]

While I am very tempted to do just that or at least to throw out the -Sc from the default fpc.cfg marcov is also right that this is not very realistic. Keeping them in does however not mean that we'll extend them in any way. They should not have been added in the first place and also shouldn't have been added to the default fpc.cfg.

Would it be feasible to compromise and only allow them to be applied to constants, i.e. /= 2 etc.?

MarkMLl

[Thaddy]

That works: the code path is rather simple, but it would take *a lot* more code to only accept constants. Your case it catered for, because the code path doesn't change. (That's to some extend the beauty)

[mercurhyo]

Code: Pascal  [Select][+][-]

1. {$TROLLMODE ON} // See https://wiki.freepascal.org/ ahahahahah
2. // New features don't necessarily mean a better future.
3. // They always complain about wanting new language features.
4. // It sounds like idiotic echoes!
5. // Pascal needs no new features to remain GREAT —
6. // just good vibes and passionate "D"evelopers!

[Thaddy]

Code: Pascal  [Select][+][-]

1. {$TROLLMODE ON} // See https://wiki.freepascal.org/ ahahahahah
2. // New features don't necessarily mean a better future.
3. // They always complain about wanting new language features.
4. // It sounds like idiotic echoes!
5. // Pascal needs no new features to remain GREAT —
6. // just good vibes and passionate "D"evelopers!

There is no new feature.
 It is a bug fix.
A breach of a promise that /= works like C.
It is also in line with {$coperators on} and only follows its original premise: ihelps translating C code.
Nothing more, nothing less.

For the umptiest time.

Reading is an art, it seems.....


Half of you can not even see it is a bug fix instead of a new feature.
Otherwise every bug fix is a feature.

Such stupidity makes me cry (virtually, don't worry), trolling or not...

I don't like the feature, but when you also decide that the feature won't be removed then at least FIX THE BUG!!! in that unwanted feature.

[mercurhyo]

@Thaddy
 
See? I also can use smileys !

[Thaddy]

 

But do you understand the difference between a bug fix and a feature.....

In my opinion IQ levels are below the new Trump mark and that is below Kelvin.

[mercurhyo]

 
No ! I started programming 5 mins and a half earlier, sir.

[Thaddy]

Ok, what is the difference between a bug fix and a feature?
Explain why I am wrong. You can't...