[ast-developers] namespace com.foo.bar.baz support (was:Re: AT&T Software Technology ast alpha software download update)

[Irek Szczesniak]

cc: wendlin1974 at gmail.com
Subject: Re: Re: [ast-developers] AT&T Software Technology ast alpha software download update
--------
I deferred all the namespace changes to a later release.
I addition to types in namespaces, there is also the question of
nested namespaces. When I added namespaces I was envisioning
a nested namespace model and namepace names would be identifiers.
The alternative, which Roland sent a patch for allows does not allow
for nesting, but allows namespaces to be named by a compound variable.
Thus, resarch.att.com could be the name of a namespace, but that does
not mean that research.att is a namespace and that of I am in
research.att.com, that if there is a namespace named research.att,
that it will be searched. I just means that variables not found
in research.att.com will be searched for in the global namespace.

That would be the java approach which is IMO more sane. Otherwise you
get into a lot of trouble for deeper-nested names such as namespace
com.ge.healthcare.project.ravenna.util.net.http.core ...

The issue with namespace types that needs to be worked out is
how the namespace for type names will be handled. Currently gobal types
are kept in .sh.type.typename. I suspect that types defined in
namespace foo, should be kept in .foo.sh.type.typename but I haven't
modified the code for this.

Why do you need code for this? For now, with Roland's patch, the code
worked fine except for arithmetic expressions. That was AFAIK the
major issue which prevented us to exploit the feature. That may be
also the only bug which should be fixed as *soon* as possible because
it will enable people to test the feature in-depth and contribute
feedback.

Irek

[David Korn]

cc: ast-developers at lists.research.att.com wendlin1974 at gmail.com
Subject: Re: namespace com.foo.bar.baz support (was:Re: [ast-developers] AT&T Software Technology ast alpha software download update)
--------

Post by Irek Szczesniak
Why do you need code for this? For now, with Roland's patch, the code
worked fine except for arithmetic expressions. That was AFAIK the
major issue which prevented us to exploit the feature. That may be
also the only bug which should be fixed as *soon* as possible because
it will enable people to test the feature in-depth and contribute
feedback.
Irek

As far as I know, Rolands patch just allowed compound variable names
for namespace and eliminted nested namespaces. I didn't see a patch
for type definitions in the namespace.

David Korn
dgk at research.att.com

[Lionel Cons]

Post by David Korn
cc: ast-developers at lists.research.att.com wendlin1974 at gmail.com
Subject: Re: namespace com.foo.bar.baz support (was:Re: [ast-developers] AT&T Software Technology ast alpha software download update)
--------

Post by Irek Szczesniak
Why do you need code for this? For now, with Roland's patch, the code
worked fine except for arithmetic expressions. That was AFAIK the
major issue which prevented us to exploit the feature. That may be
also the only bug which should be fixed as *soon* as possible because
it will enable people to test the feature in-depth and contribute
feedback.
Irek

As far as I know, Rolands patch just allowed compound variable names
for namespace and eliminted nested namespaces.

Where are nested namespaces? If you mean namespace foo { namespace bar
{} } to access .foo.bar - that never worked.

Lionel

[Lionel Cons]

Post by Lionel Cons

Post by David Korn
cc: ast-developers at lists.research.att.com wendlin1974 at gmail.com
Subject: Re: namespace com.foo.bar.baz support (was:Re: [ast-developers] AT&T Software Technology ast alpha software download update)
--------

Post by Irek Szczesniak
Why do you need code for this? For now, with Roland's patch, the code
worked fine except for arithmetic expressions. That was AFAIK the
major issue which prevented us to exploit the feature. That may be
also the only bug which should be fixed as *soon* as possible because
it will enable people to test the feature in-depth and contribute
feedback.
Irek

As far as I know, Rolands patch just allowed compound variable names
for namespace and eliminted nested namespaces.

Where are nested namespaces? If you mean namespace foo { namespace bar
{} } to access .foo.bar - that never worked.

I looked at the patch, it removed a simple check for '.' characters in
the namespace name. That doesn't remove support for nested namespaces
(which, IMO, are of doubtful use compared to namespace
com.foo.bar.baz), does it?

Lionel

PS: I'd like to underline the importance of namespace com.foo.bar.baz
to us as large, diverse organisation. A solution like namespace
com.foo.bar.baz would give us finally the tool to build large shell
function libraries.

[Wendy Lin]

Post by Lionel Cons

Post by Lionel Cons

Post by David Korn
cc: ast-developers at lists.research.att.com wendlin1974 at gmail.com
Subject: Re: namespace com.foo.bar.baz support (was:Re: [ast-developers] AT&T Software Technology ast alpha software download update)
--------

Post by Irek Szczesniak
Why do you need code for this? For now, with Roland's patch, the code
worked fine except for arithmetic expressions. That was AFAIK the
major issue which prevented us to exploit the feature. That may be
also the only bug which should be fixed as *soon* as possible because
it will enable people to test the feature in-depth and contribute
feedback.
Irek

As far as I know, Rolands patch just allowed compound variable names
for namespace and eliminted nested namespaces.

Where are nested namespaces? If you mean namespace foo { namespace bar
{} } to access .foo.bar - that never worked.

I looked at the patch, it removed a simple check for '.' characters in
the namespace name. That doesn't remove support for nested namespaces
(which, IMO, are of doubtful use compared to namespace
com.foo.bar.baz), does it?
Lionel
PS: I'd like to underline the importance of namespace com.foo.bar.baz
to us as large, diverse organisation. A solution like namespace
com.foo.bar.baz would give us finally the tool to build large shell
function libraries.

David, could you just apply Roland Mainz's patch to enable namespace
com.foo.bar.baz for the next release, please?
I'd be very grateful about it.

Wendy