My comments
> * The Complete Edition of Euphoria now provides a -scramble
> option of bind and shroud to improve the security of programs
> that you distribute.
I like this idea.
> * Some optimizations were added. The following general forms
> of expression are now faster:
>
> 2 * x
> x * 2
> 1 + x
>
> where x can be any expression, and have type atom or
> sequence
Does this not also cover integers?
>
> * There is a new documentation file, PERFORM.DOC with lots of
> tips for performance-obsessed programmers.
This will help me dramatically.
> * A new -clear_routines option of bind and shroud will leave the
> names of all routines unshrouded. This is necessary if your
> program calls routine_id(). You'll be warned if you use
> routine_id() and do not choose this option. (Registered users
> can use -scramble together with -clear_routines to restore a
> high level of shrouding.)
Good. although I don't use routine_id() yet. It will be
helpful to many.
> * A new documentation file, BIND.DOC describes all the features
> of bind.bat and shroud.bat. The previous description in
> REFMAN.DOC has been shrunk.
This will make it easier to find how to use bind and shroud.
> * The file, OVERVIEW.DOC gives a quick overview of all
> documentation files.
Great Idea.
-------------------------------------
Setting values at declaration:
integer x = 5
I feel it will complicate the code and make the interpreters job harder.
--------------
The following is an excellent Idea BUT I feel that it makes the code harder
to read.
variable = function( self, value )
------------
The following saves keystrokes. But I don't like its readability.
I don't think it is worth it.
a =+ 1
-----------
> Currently, the environment variable EUDIR contains a single
> directory specification, which is used by Euphoria to determine
> the location of include files.
>
> I think it would be nice to allow this variable to contain
> multiple directories, _ l_ PATH.
I think this Idea should be considered. Either that or having the
Euphoria search the PATH after searching EUDIR.
None of my extra includes are kept in the euphoria directory.
Doing so would make it very difficult to install the next release
of Euphoria.
-------------
I saw the following format used in PERL.
{ x, y } = get_position()
It took me a moment to get use to it but I find that it would
be very useful. Another example:
{BMPpalette, BMPimage} = read_bitmap("bitmap.bmp")
-------------
My personal Opinion on the following:
variable = variable[6..end]-- end meaning length(variable)
I hate it. I don't exactly like having to type length(variable)
every time but it is much more readable. It makes deciphering
somebody else's code, or better yet Code that I built ages ago,
much easier to understand.
-------------
My opinion on base-0.
I would like to have the option of 0-base but it would crash all
existing code. The only way to prevent it from crashing existing
code would be the following: with base-0
I suggest not doing it.
-------------
I would actually like to see the use of an operator for power.
But as you said; power isn't use that much.
-------------
procedure foo() end procedure
VS
procedure foo() {}
I actually prefer the extra typing. It serves as a reminder when
I get to the end of the procedure/function that I should or
shouldn't return a value. I know that sounds like a weak argument
but consider that you are Rewriting OLD code. And that near
the end of the code you start wondering again. Is this a procedure
or a function. You can simply move to the END of the code or to the
beginning. ALSO it is much easier to spot "end function" than it
is to spot }. one thin little character can be easily overlooked.
It could lead to an accident such as:
function bob() {
return 0
}
}
-------------
procedure vs. function:
I am use to the BASIC's I like have function and procedure separated.
It allows the reader to quickly see that it will/won't return a value.
It should/shouldn't be assigned to something.
-------------
compare()
Ah. I think everyone should just get over it.
compare() is the most logical method.
The only other idea I have is to implement eq, ne, gt, lt instead.
I really don't want that to occur. It looks to much like ASM.
--------------
global exception handler
This is definitely needed.
----------------------------------------------------------
-- Lucius L. Hilley III -- lhilley at cdc.net --
-- of -- --
-- Hollow Horse Software -- http://www.cdc.net/~lhilley --
----------------------------------------------------------
|
Not Categorized, Please Help
|
|
