Re: ver4 keyword Conflict

new topic     » goto parent     » topic index » view thread      » older message » newer message
jimcbrown said...
mattlewis said...
BRyan said...

I understand about name space, but I still think that if you have standard libraries then

all Math functions should be located in a standard Math library.

This was one of the initial goals for having standard libraries.

Anything implemented in euphoria or via machine_func or machine_proc goes into the standard library. tan has always been a built-in. Likewise, puts is still built-in, and not located in std/io.e. I don't foresee tan (or, e.g., sin, sqrt) going anywhere.

Matt

While my preference would be to turn tan() into a machine_func() and expose it via std/math.e - for the same reasons that BRyan does, this would be breaking backwards compatibility with Euphoria 1.x, 2.x, 3.0, 3.1.1, 4.0, 4.0.1, 4.0.2, and 4.0.3.

I'm not sure what the fuss is about. It just means

?tan(0.5) 

would have to become

include std/maths.e 
?tan(0.5) 

Is that really such a deal breaker?

Pete

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

Search



Quick Links

User menu

Not signed in.

Misc Menu