perl-css-devel

[css] URI namespace clash using CSS::SAC::LexicalUnit

[Bjoern H. <der...@gm...>]

Hi,

   use CSS::SAC::LexicalUnit ':constants'; imports vital constants into
the current namespace, so the URI constant. But I want to use the URI
module. Is there anything I can do to have my

  my $base = URI->new(...);

excluding using fully qualified CSS::SAC::LexicalUnit::URI etc.pp.? If
not (I don't think so, though), 'URI' is probably a bad name for the
constant.

regards,
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

Re: [css] URI namespace clash using CSS::SAC::LexicalUnit

[Robin B. <ro...@kn...>]

On Monday 22 October 2001 01:25, Bjoern Hoehrmann wrote:
>    use CSS::SAC::LexicalUnit ':constants'; imports vital constants into
> the current namespace, so the URI constant. But I want to use the URI
> module. Is there anything I can do to have my
>
>   my $base = URI->new(...);
>
> excluding using fully qualified CSS::SAC::LexicalUnit::URI etc.pp.? If
> not (I don't think so, though), 'URI' is probably a bad name for the
> constant.

One solution is to rename all constants to be prefixed with SAC_, make 
*those* importable with :constants, and for a while the unprefixed ones 
importable as well with :old_constants. This might be the cleanest solution.

Note that you can also:

*Your::Package::SAC_URI = \&CSS::SAC::LexicalUnit::URI;

to get an alias usable locally as SAC_URI.

-- 
_______________________________________________________________________
Robin Berjon <ro...@kn...> -- CTO
k n o w s c a p e : // venture knowledge agency www.knowscape.com
-----------------------------------------------------------------------
In which level of metalanguage are you now speaking?

Re: [css] URI namespace clash using CSS::SAC::LexicalUnit

[Bjoern H. <der...@gm...>]

* Robin Berjon wrote:
>On Monday 22 October 2001 01:25, Bjoern Hoehrmann wrote:
>>    use CSS::SAC::LexicalUnit ':constants'; imports vital constants into
>> the current namespace, so the URI constant. But I want to use the URI
>> module. Is there anything I can do to have my
>>
>>   my $base = URI->new(...);
>>
>> excluding using fully qualified CSS::SAC::LexicalUnit::URI etc.pp.? If
>> not (I don't think so, though), 'URI' is probably a bad name for the
>> constant.
>
>One solution is to rename all constants to be prefixed with SAC_, make 
>*those* importable with :constants, and for a while the unprefixed ones 
>importable as well with :old_constants. This might be the cleanest solution.
>
>Note that you can also:
>
>*Your::Package::SAC_URI = \&CSS::SAC::LexicalUnit::URI;
>
>to get an alias usable locally as SAC_URI.

Yes, and it is also possible to create an URI object first and then
import those symbols but I think your solution is probably the best
one. Would you mind patching it into CVS?

regards,
-- 
Björn Höhrmann { mailto:bj...@ho... } http://www.bjoernsworld.de
am Badedeich 7 } Telefon: +49(0)4667/981028 { http://bjoern.hoehrmann.de
25899 Dagebüll { PGP Pub. KeyID: 0xA4357E78 } http://www.learn.to/quote/

Re: [css] URI namespace clash using CSS::SAC::LexicalUnit

[Robin B. <ro...@kn...>]

On Tuesday 23 October 2001 22:20, Bjoern Hoehrmann wrote:
> Yes, and it is also possible to create an URI object first and then
> import those symbols but I think your solution is probably the best
> one. Would you mind patching it into CVS?

Which solution do you prefer ? The one that consists of prefixing all the=
=20
constants ? I was thinking of doing it anyway, it's much better. I can't =
do=20
it now but I've added it to the TODO.

--=20
_______________________________________________________________________=0D
Robin Berjon <ro...@kn...> -- CTO=0D
k n o w s c a p e : // venture knowledge agency www.knowscape.com=0D
-----------------------------------------------------------------------=0D
Avoid clich=E9s like the plague.=0D
=0D