Wish "With" statement?

Hi,

I don't know if it was asked before or even if there's already a BASiC counterpart, but would you consider the introduction of a statement like "with" in Pascal/Delphi?

In that language is used this way:

with MyObject do
begin
left = 12
top = 20
text = "hello"
end

Or using it on an Array we could have:

with MyNewArray do
begin
if lenght > 0 then ...
clear
end

Just my 2cents to the wishlist..

Umberto

+1

+1

In vb6 it was like this (i think)

in delphi it is

Just curious since I never was into Delphi. What does this do more than setting some object properties?

@nikolaus
Quoting from DelphiBasics:

The With keyword is a convenience provided by Delphi for referencing elements of a complex variable, such as a record or object.

It simplifies the code by removing the need to prefix each referenced element with the complex variable name.

Click to expand...

The VB way of prepending a dot could be safer for disambiguity concerns, but I'm an old Turbo Pascal 1.0 fan...

ok, then

+1

Just my $0.02 worth. I eat, sleep, and breath pascal! But the with clause is one I just don't see much use in.
I know, there's a little advantage when dealing with large arrays of records. Basically, instead of making a far pointer call to access each element of the record, you access it near pointer as a local variable. The problem I have with it is some folks like to confuse things like:

With Message, File, Configuration, TempMemory DO BEGIN
Area := 1;
Description := 'next';
File := '\files\myfile.zip';
END;

Now, with the above, does area belong to Message or File? Does File specify the file the message is stored in, or the file your adding to the file database? If Area exist in Message and File, which one gets set, or both? Too many IF's, and too many programmers leave too much to guessing!
Personally, with the way Basic4Android handles things, I don't see myself using it. I won't complain if a feature is added... What you need to consider is how it's going to effect the output. If Java has no with statement (which I don't think it does), then it will just end up saving you time of having to type eg. MessageRec. in front of the variable name. In which case, it wouldn't save you any space or speed up anything.

Hi John,

I agree with you about the perils inherent in the with-statement misuse, indeed a long debated point among Pascal programmers.
But as a knive could be used to slice bread and to kill, so the with-statement could be put in good or bad use. It's all up to us, programmers (and cooks ..eheh).
Anyway, to avoid most problems an eventual with-statement alike could be restricted to a single variable name (or object), something like:
with <single complex var> do
<statements>
</with>

Umberto

+1 VB6-like implementation would be very useful!

+1

I miss this from my Delphi days - made my code easier to write AND read.

-1
From what I understand, Delphi is moving away from the "With". I don't use it anymore as it causes a lot of issues (in delphi code). In theory it's a good "cheat" but in reality it seems to open the door to problems so I would not be too concerned about getting "with" in the language. I'd rather see real useful stuff added like optional parameters (with default values), "class" const, variables and methods (they work class wide vs instance wide), built in "result" variable for functions, templates for layouts, views, etc (for example, I prefer my panels to not have rounded corners).

I also remember this from vb6/vbscript/asp. when I first saw it I couldn't really get what it was doing.

When I look at it now I see the benefit of less typework.

On the other hand my mind doesn't think of using it as the traditional methods come up faster.

But it could be a nice addition ofcoz.

in VB6 its had some performance benefits also

if you used some think like this


it opens the form, subform , object and set the 3 options
but if you did it like :


then it opens the form, subform, object set option and then close all and with next line it opens form, subform, object again.
with example as above the performance gain was minimal but for reading it was easier but if you had big forms, subforms and lot of
objects to set the performance benefit could be big (special with big form or recordsets)

i dont know if in b4a there is a performance benefit but for reading i would like to have it.

+1 Save some time when you do Find and Replace. Less typing and more readable code. It makes VB6 programmer like me happy.

I have also requested this in the past.
+1 from me!

+1