Delphi中TRec记录验证后未变更问题求助（附代码示例）

Hey Steve, let's break down why your TRec record isn't updating as expected after validation—this is a super common gotcha with Delphi's value types like records! Let's start with the core issue, then walk through practical fixes.

The Root Cause: Records Are Value Types #

In Delphi, records are value types, not reference types (like classes). That means whenever you access a record property (like Rec in TParameterRec), you're getting a copy of the underlying fRec field—not a direct reference to it. If you modify fields on that copy (e.g., MyParam.Rec.Name := 'Test'), you're only changing the temporary copy, not the original fRec stored in TParameterRec.

Looking at your code structure:

TRec = record 
  Name: string; 
  Age: string; 
  // Other fields...
end; 

TParameterRec = record 
private 
  fRec: TRec; 
  procedure SetRec(Value: TRec); 
public 
  property Rec: TRec read fRec write SetRec; 
end; 

TSampleClass = class 
private 
  fParameter: TParameterRec; 
  // Rest of your class code
end;

Let's cover the most likely fixes based on your setup.

Fix 1: Modify a Copy, Then Reassign #

If you need to keep your current structure, the simplest (though clunky) fix is to explicitly work with a copy and reassign it:

1. Grab a copy of the Rec property
2. Modify the copy's fields
3. Assign the modified copy back to the Rec property

Example code:

var
  TempRec: TRec;
  MySample: TSampleClass;
begin
  MySample := TSampleClass.Create;
  try
    // Get a copy of the record
    TempRec := MySample.fParameter.Rec;
    // Modify the copy
    TempRec.Name := 'Updated Name';
    TempRec.Age := '30';
    // Assign the modified copy back to the property
    MySample.fParameter.Rec := TempRec;
  finally
    MySample.Free;
  end;
end;

This works because you're explicitly updating the underlying fRec via the SetRec setter.

Fix 2: Add Encapsulated Methods to Modify Fields #

A cleaner approach is to add methods to TParameterRec that directly modify the underlying fRec fields. This avoids dealing with copies entirely:

Update TParameterRec:

TParameterRec = record 
private 
  fRec: TRec; 
  procedure SetRec(Value: TRec); 
public 
  property Rec: TRec read fRec write SetRec; 
  // Add methods to modify individual fields
  procedure SetName(const AName: string);
  procedure SetAge(const AAge: string);
  // Add methods for other fields as needed
end;

Implement the methods:

procedure TParameterRec.SetName(const AName: string);
begin
  fRec.Name := AName;
end;

procedure TParameterRec.SetAge(const AAge: string);
begin
  fRec.Age := AAge;
end;

Now you can modify fields directly without copy issues:

MySample.fParameter.SetName('Updated Name');
MySample.fParameter.SetAge('30');

Fix 3: Use Record References (Delphi 10.3+) #

If you're using Delphi 10.3 or newer, you can leverage record property references to get direct access to the underlying fRec field. Modify TParameterRec to include a property that returns a reference:

TParameterRec = record 
private 
  fRec: TRec; 
  procedure SetRec(Value: TRec); 
public 
  property Rec: TRec read fRec write SetRec;
  // Reference property to access the original record directly
  property RecRef: TRec read fRec write fRec;
end;

Now you can modify fields directly via the reference property:

MySample.fParameter.RecRef.Name := 'Updated Name';
MySample.fParameter.RecRef.Age := '30';

This skips the copy entirely, as RecRef points directly to fRec.

Bonus: Check Your SetRec Implementation #

Double-check that your SetRec procedure is correctly assigning the value to fRec. It should look like this:

procedure TParameterRec.SetRec(Value: TRec);
begin
  fRec := Value;
end;

If there's logic here that's not properly updating fRec (e.g., missing assignment, conditional checks that block the update), that would also prevent your record from changing.

Quick Checklist to Debug #

1. Are you modifying a temporary copy of the record instead of the original?
2. Does your SetRec procedure correctly assign the input value to fRec?
3. Are you passing TParameterRec around as a value (creating copies) instead of keeping a single instance?

内容的提问来源于stack exchange，提问作者Steve88