Welcome to the Lounge

Mike Hankey wrote:

I'm so old I was the counter for Noah

I was busy picking out two of the female species to load

Ralf Quint wrote:

you have multiple records/objects with the same names for data (of the same TYPE) or methods/procedures/functions, you can not be sure which one might be called/referred to.

procedure P;
  var C: integer;

  procecdure Q;
    var C: integer;
    begin
      C:= 1;
    end;

  begin
    { some other code }
  end;

with A do
  with B do 
  begin
    C:= 1;
  end;

with A, B do

with A do
  with B do 

Ralf Quint wrote:

Very interesting that you are trying to explain how Pascal works to someone who is programming in various versions of Pascal, as the main programming language, for 48 years now.

within the nested WITH statements (regardless of how you write it), it IS POSSIBLE to create an unintentional ambiguity

which is NOT guaranteed to be always have the same precedence

it clearly shows that you have not worked with a lot of different Pascal implementations

calling methods of the same name in different objects, so something like

with A, B do
begin
C ("foo");
C ("bar");
end;

And the application of scopes within nested procedures/functions, that is completely different issue. THAT is clearly defined.

But that would be also not related to the initial post of this thread.

var myFluentThing := TFluentThing.Create
  .DoThis(x)
  .DoThat(y)
  .DoAnother(z);

IThing thing = new ThingBuilder()  // returns ThingBuilder instance
    .AddTitle("I'm a Thing!")      // returns same ThingBuilder instance
    .CreatePreciousThing()         // returns PreciousThing instance
    .SetPreciousLevel(100);        // returns same PreciousThing instance
// thing is now a PreciousThing instance

int i = new FooBuilder()
            .Build()
            .DoSomethingToFoo()
            .DoSomethingElseToFoo()
            .GetAnEnumerableIntPropertyOfFoo()
            .Sum();

Wordle 1,065 6/6

⬛⬛⬛⬛⬛
⬛🟩🟩🟨⬛
⬛🟩🟩⬛⬛
⬛🟩🟩🟩🟩
⬛🟩🟩🟩🟩
🟩🟩🟩🟩🟩