# Forcing ETL namespace

**URL:** https://forums.synfig.org/t/forcing-etl-namespace/9938
**Category:** Development
**Created:** [July 6, 2019, 5:09pm UTC](https://forums.synfig.org/t/forcing-etl-namespace/9938 "2019-07-06T17:09:27Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![rodolforg](https://forums.synfig.org/letter_avatar_proxy/v4/letter/r/c68b51/32.png) [@rodolforg](https://forums.synfig.org/u/rodolforg)
#### Post date: [July 6, 2019, 5:09pm UTC](https://forums.synfig.org/t/forcing-etl-namespace/9938/1 "2019-07-06T17:09:27Z")

</div>

I’m trying to help to improve Synfig, specially for user interface/usability issues - and performance.

However, I know the code has a long-dated legacy and ETL is always there in the way.  
So, I started to look at it and now [I’m trying to clean it up a bit](https://github.com/synfig/synfig/pull/876).

My question here is: Is ETL used in another project besides Synfig? I want to remove the unused “`ETL_FLAG_NONAMESPACE`” and, together, force usage of ETL namespace directly by `namespace etl {`, instead of keeping the macro `_ETL_BEGIN_NAMESPACE`.

The Synfig-core makes use of “etl::” namespace directly, so I think this kind of macro useless.

---

<div class="post-metadata">

### Author: ![KonstantinDmitriev](https://forums.synfig.org/user_avatar/forums.synfig.org/konstantindmitriev/32/3_2.png) [@KonstantinDmitriev](https://forums.synfig.org/u/KonstantinDmitriev)
#### Post date: [July 9, 2019, 11:02am UTC](https://forums.synfig.org/t/forcing-etl-namespace/9938/2 "2019-07-09T11:02:54Z")

</div>

Hi @rodolforg! My name is Konstantin Dmitriev, I am maintainer of Synfig. Thank you for your interest and welcome to the project!

ETL is not used in any other project besides Synfig, so it is safe to do as you suggesting. Eventually, it will be nice to merge ETL into synfig-core to avoid extra build step. 🙂

---

<div class="post-metadata">

### Author: ![rodolforg](https://forums.synfig.org/letter_avatar_proxy/v4/letter/r/c68b51/32.png) [@rodolforg](https://forums.synfig.org/u/rodolforg)
#### Post date: [July 9, 2019, 11:22am UTC](https://forums.synfig.org/t/forcing-etl-namespace/9938/3 "2019-07-09T11:22:31Z")

</div>

Nice 🙂

Any chance of [https://github.com/synfig/synfig/pull/876](https://github.com/synfig/synfig/pull/876) being merged?  
So I’d change namespace after this PR in order to avoid merge conflicts.

---

<div class="post-metadata">

### Author: ![KonstantinDmitriev](https://forums.synfig.org/user_avatar/forums.synfig.org/konstantindmitriev/32/3_2.png) [@KonstantinDmitriev](https://forums.synfig.org/u/KonstantinDmitriev)
#### Post date: [July 9, 2019, 11:35am UTC](https://forums.synfig.org/t/forcing-etl-namespace/9938/4 "2019-07-09T11:35:50Z")

</div>

I am testing it now. Thank you! 🙂

---

<div class="post-metadata">

### Author: ![rodolforg](https://forums.synfig.org/letter_avatar_proxy/v4/letter/r/c68b51/32.png) [@rodolforg](https://forums.synfig.org/u/rodolforg)
#### Post date: [July 10, 2019, 1:27am UTC](https://forums.synfig.org/t/forcing-etl-namespace/9938/5 "2019-07-10T01:27:59Z")

</div>

> [@rodolforg](#):
>
> The Synfig-core makes use of “etl::” namespace directly, so I think this kind of macro useless.

So it’s done 😉

> <https://github.com/synfig/synfig/pull/879>
>
> The Synfig-core makes use of “etl::” namespace directly
> almost everywhere.
> so …I think this kind of macro useless.
> 
> 'Discussed' here:
> https://forums.synfig.org/t/forcing-etl-namespace/9938