1. RE: Revised Namespace Proposal
> I've come up with a -- solution
It sounds great. Go with it.
2. RE: Revised Namespace Proposal
Robert Craig wrote:
> I'll also allow quotes around included file names,
> in case someone wants to include a name with blanks in it, e.g.
>
> include "Program Files\\myfile.e"
>
> Otherwise the quotes aren't needed,
> and blank (whitespace) terminates the file name.
Rob:
I think this is NOT a good idea.
I see no necessary use for this feature.
I think it is going to come back to haunt you
and cause errors for your DOS users.
This create unnecessary questions and errors.
I will bet if you conduct a survey not .05% of
the users will need this.
Please only add the features that everyone really needs.
Bernie
3. RE: Revised Namespace Proposal
Derek Parnell wrote:
> Hi Bernie,
> ,,,,,,,,,
> Derek Parnell
> Melbourne, Australia
> "To finish a job quickly, go slower."
Derek:
I feel this feature is of no advantage.
If a user is using include files then they should be in the
Euphoria include directory, this directory is used for
DOS so it probably doen't have spaces.
If you are giving a client/user a compiled or bound Application
then the application is going to be launched by/from
windows ( which will the directory ).
Some users have written install programs, Are they going to
then use spaces in their install programs ?
What happens to the DOS users on the list that can only
aford to use a version of DOS that doesn't supports
spaces ? What happens if they create a directory with a
space in it with Euphoria.
I have been waiting on the list for 3 years for improvements
to be made to Euphoria and I do not think that these kind of
features should be added until more important features are
added such as :
1. a better foward references solution
2. inline assembler
3. a easier interfacing to other langagues.
Of course that is my opion whether anyone agrees
with me I don't know.
Bernie
4. RE: Revised Namespace Proposal
Robert Craig wrote:
> I read through the suggestions that people put forward
> last week regarding the namespace issue, ...
> If anyone can see a simple way to improve ...
> please post it to this list. ...
> Rob Craig
-- Hello Rob,
-- A new keyword "with_global" may give a simple way to define
-- a unique global symbol MYSYMBOL
-- even when the symbol MYSYMBOL is already defined as global
-- by 2 (or more) included files e.g. MYFILE1.E and MYFILE2.E
-- if
include MYFILE1.E
include MYFILE2.E with_global MYSYMBOL
-- then MYSYMBOL is the global MYSYMBOL defined into MYFILE2.E
-- elseif
include MYFILE1.E with_global MYSYMBOL
include MYFILE2.E
-- then MYSYMBOL is the global MYSYMBOL defined into MYFILE1.E
-- elseif
include MYFILE1.E with_global MYSYMBOL
include MYFILE2.E with_global MYSYMBOL
-- then it is an error
-- elseif
include MYFILE1.E
include MYFILE2.E
-- then the interpreter gives an warning
-- and/or (may be) an error when MYSYMBOL will be used somewhere
-- it should be possible to code:
include SOMEFILE.E with_global MYSYMBOL1, MYSYMBOL2, MYSYMBOL3 ...
-- If the symbol MYSYMBOL is not defined into MYFILE.E then
include MYFILE.E with_global MYSYMBOL
-- is an error
-- Here are some synonyms for the new keyword "with_global":
"with global" -- if there is no parse problem...
"including_global"
"including global" -- if there is no parse problem...
"including"
In hopes of helping... Sincerly
(a french speaking old programmer from Belgium)
Gilbert Lemaitre
5. RE: Revised Namespace Proposal
On 10 Jul 2001, at 16:36, Gilbert Lemaitre wrote:
>
>
> Robert Craig wrote:
> > I read through the suggestions that people put forward
> > last week regarding the namespace issue, ...
> > If anyone can see a simple way to improve ...
> > please post it to this list. ...
> > Rob Craig
Some of these namespace suggestions are really getting confusing to me.
How about a simple assignment, local to the file the assignment is made?
win. = include { "win32lib.ew","-abs"}
win. = include {"e:/math/eu libs/intmath.ew","abs"}
That would drop intmath's abs() into my code in place of win32lib's abs(), for
whatever reason i haven't thought of yet.
win. = include { "win32lib.ew","-abs"}
int. = include {
{"e:/math/eu libs/intmath.ew","abs"},
{"d:/graphics/vectormath.ew","3d.distance.*"}
}
str. = include {
{"d:/euphoria/string libs/strtok.ew"},
{"d:/euphoria/string libs/strings.ew","left","right","mid"},
{"d:/euphoria/string libs/strmath.ew","abs","add","divide"}
}
So i don't have the "attempt to redefine abs()" error,
and all the string code i included would all be seen as
str.mid() -- from strings.ew
str.right() -- from strings.ew
str.parse() -- from strtoks
str.gettok() -- from strtoks
int.abs() -- from intmath.ew, not win32lib
str.abs() -- from strmath.ew
but in my program only, no passing of my namespaces happens for
programs that include my file, unless i provide a "global functioname()".
Kat
