Namespaces in Spring4d code

[EugeneK 22]

Hi

 

Is there any chance that namespaces will be added in Spring4d code? e.g. System.SysUtils instead of SysUtils

[Stefan Glienke 2059]

Why?

[EugeneK 22]

In my projects I don't have anything in 'Unit Scope names' and 'Unit aliases', so it won't compile if I just add it as is. All other 3rdparty libraries that I use have it, so I don't want to add it back.

[Anders Melander 1912]

30 minutes ago, Stefan Glienke said:

Why?

Supposedly compiles faster...?

[Zoran Bonuš 12]

34 minutes ago, Stefan Glienke said:

Why?

I guess to help the compiler a liittle bit,  as explained here:

https://blog.marcocantu.com/blog/2022-december-suggestions-help-delphi-compiler.html

[Stefan Glienke 2059]

The claim that it compiles faster is bogus - prove me wrong. Most compile time from spring4d comes from generics, which I reported years ago.

Also, my suggestion for third-party libraries is to pre-compile them, which removes any dependency on the project options in your project.

 

Currently, Spring4d supports down to XE, and as long as that is the case, I am not putting even more conditionals into the code than there already are.

[EugeneK 22]

37 minutes ago, Anders Melander said:

Supposedly compiles faster...?

Also it forces unified style across all the code and improves readability.

[Anders Melander 1912]

35 minutes ago, EugeneK said:

improves readability

I'm not sure I agree on that.

 

I've just been through a refactoring session where SysUtils was replaced with System.Sysutils which in turn made it necessary to resolve a series of type references as System.Sysutils.PByteArray instead of Sysutils.PByteArray due to a duplicate type declaration. That certainly didn't improve readability.

[Kryvich 166]

Embarcadero can sometimes move system types and functions from one RTL unit to another. Should we care in which specific RTL module a particular system type is declared? The Unit Scope Names setting helps abstract away implementation details.

Edited 2 hours ago by Kryvich

[baoquan.zuo 26]

There is one approach without using many conditional defines:

- Just use fully qualified/scoped unit names in use clauses

- Create a shared .optset to be used by all XE-specific projects

- Use unit aliases to map System.SysUtils to SysUtils, System.Actions to System (Ignore it), etc. in the optset.

 

I did try this way and I am OK with it, but I am not sure what is the limit of the unit aliases/performance boost, an you have to use conditional defines when reference full-qualified type/members of RTL (should be limited).

[Anders Melander 1912]

1 hour ago, Kryvich said:

The Unit Scope Names setting helps abstract away implementation details.

Huh? How do they do that?

Can you give an example?