Re: namespace

new topic     » goto parent     » topic index » view thread      » older message » newer message

-------Phoenix-Boundary-07081998-

Hi Jiri Babor, you wrote on 7/11/02 3:52:53 AM:

>
>Hi, Karl. You wrote:
>
>I think you have a point. A global constant should be both
>global and constant! I have modified Bliss to enforce this, but
>to allow duplicate definitions (many files can do 'global FALSE =3D 0').
>
>Duplicate definitions are not terribly clean, but since they are also 
>completely
>harmless I can live with them ;).
>

I have had a change of heart here. The Euphoria approach of
allowing all redefinitions seems correct. The meaning of an
id is determined first by the current subprogram, then by the
program, and finally by the external file. It might be useful to
have a 'lint' option that would warn about this and the
re-definition of built-ins.

>Bliss now allows classes to have constants as members which
>opens up some maybe useful namespacing techniques.
>
> class Windows_constants
>     constant
>     BN_KILLFOCUS =3D 7,
>     BN_CLICKED =3D 0
>     -- You could probably think of a few more!
>  end class
><snip>
>
>Interesting. But I hasten to add I have never been a fan of OO
> techniques as such; in my opinion they are the principal cause
> of the enormous software bloat of the last decade. I suppose
> it's one of those ideas that were just too much ahead of their
> time: only quite recently computers acquired sufficient memories,
>storage capacities and the processing power to deal, adequately,
> with attendant requirements.
>
I too have been (and remain) deeply suspicious of OO. Their
main usefulness seems to be in a few specific kinds of complex
programs such as GUI's. But I also see classes and dot-notation
as very powerful tools for producing cleaner procedural code.
Another way of expressing and controlling modularity is helpful.
Bliss does not have virtual methods, co- or contra-variance, or
polymorphism (beyond that provided by sequences).

>
>I am also sorry I cannot comment on your baby, since I have
> not studied Bliss in any detail. Perhaps just one, very
> superficial impression - I hope you will not be too offended:
> it seems to be a bit of an eclectic mixture; perhaps you 
>are trying to please too many people with too many pet ideas...
>

The intention of Bliss is to add two types of features to Euphoria:

First my pet ideas, such as slicing shorthands, variable initializations
 etc. This category has been evolving as others make suggestions, and
 may be fairly criticized as too many pet ideas.

Secondly, significant enhancements such as classes, exceptions,
 cdecl callback capability, and so forth. I think a fair criticism of
 these features might be that they create a new language  (i.e. It's not
 Euphoria any more).

I do agree that I am sometimes over-responsive to suggestions, but
this is partly a symptom of the young age of the language.
I consider Bliss to be largely complete now (with the recent addition
of member constants and initializers). I remain open to the possible
addition of useful features that don't intefere with what's
already there. 

Regards
Karl Bochert

-------Phoenix-Boundary-07081998---

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu