David Heffernan

On 9/28/2023 at 2:59 PM, dummzeuch said:

Underwhelming featurewise might just mean they focused on fixing bugs.

Usually each release comes with a bunch of bugs fixed, and a new set of bugs released into the wild. I do think the product is slowly getting better though. 

3 hours ago, FreeDelphiPascal said:

they ask me where Delphi is situated in Tiobe

Do they treat you differently when you answer? 

21 hours ago, FreeDelphiPascal said:

But it is important for us (Delphi guys) because of the publicity. Everybody knows how poor Tiobe is, still everybody is quoting it.

Who cares about TIOBE? It's just irrelevant. 

On 9/25/2023 at 4:36 PM, luciano_f said:

We urgently need more robust IDE

It's strange that if this is what you want that you ask for something else. Classic XY problem. 

19 minutes ago, Anders Melander said:

If you are running out of memory at 2.5GB then the IDE is trying to make an allocation of 0.5 GB or more. This seems unlikely so there could be something else going on. You might wait to check the size of "hardware reserved memory" on your system.

Address space fragmentation and sub allocation fragmentation. 

Love the engagement here from the poster 

Yes, but what is reporting the memory leak? There are lots of leak detection tools. If you use full fastmm then you can get allocation stack traces. 

It doesn't sound like you've really understood the issue. Normally Text would just map directly to GetText. But we still have no idea what Value is. 

This thread displays a deeper problem. That you think we can tell you what is happening with such incomplete details highlights the fact that you are also trying to solve the problem without those details. 

We can't guess what the code is. We still don't know how you are detecting. 

We've no idea what Value is. How are you detecting that there's a leak. 

14 minutes ago, Sherlock said:

Lazarus on the other hand is dogfooding at its best

Is the debugging experience still terrible though? 

How are you detecting that the memory has been leaked? 

"Material is not a valid floating point value" 

Ask yourself why you are trying to convert the text Material to a numeric value. Do you know why yet?? 

7 hours ago, Vincent Parrett said:

I certianly hope they do not migrate the IDE to 64bit anytime soon - the 64bit compiler is no where near as good as the 32bit compiler (speed, code generation) - and switching to 32bit would switch around the debugging experience

 

32bit IDE
   32 bit debugging - not great
   64 bit debugging - awful

 

64bit IDE
   32 bit debugging - awful
   64 bit debugging - not great

Careful what you wish for.

This seems extremely optimistic 

Set a break point on the line where the error occurs. When the code breaks there inspect the value of the argument passed to StrToCur. 

Find a tutorial on how yo use a debugger

The error message seems quite clear. Do you know how to use the debugger to inspect vakues being passed to StrToCurr? 

But is anybody going to get paid and have any job security?

It would really help if we could down vote issues as well as up vote them

This post here isn't going to have any impact

7 hours ago, Sherlock said:

Considering hate stems mostly from envy, I can live with that.

I'm quite sure that the people at TIOBE are driven night and day by their intense feelings of envy towards Delphi. I really can't imagine they think about anything else. 

What is the pay and working conditions? How long is the contract? 

On 9/4/2023 at 6:09 PM, tony.huerlimann said:

I have an application where the user should choose between three states: "yes it's ok", "no, it's not", "not sure". What other component could be used?

Radio group:

- Yes it's OK

- No it's not

- Not sure

22 minutes ago, PeterBelow said:

The problem in this case was that integer is 32 bit but the load address of a 64 bit DLL is 64 bits when loaded from a 64 bit project.

I know what the problem is. My point is that a negative value in a signed integer that is actually holding a pointer, does not imply that a 64 bit value was stored in a 32 bit type.

Negative integer wouldn't be a problem per se. A DLL loaded between 0x80000000 and 0xffffffff would be negative when interpreted as a signed integer.

22 minutes ago, Anders Melander said:

Yikes.

Nobody touches my screen! Not even myself.

 

Besides touch screens add cost and complexity.

I'm not a big screen toucher either