🚀 go-pugleaf

In article <2490@news.cerf.net> jcbhrb@nic.cerf.net (Jacob Hirbawi) writes:

>   Elegant tool for expressing parallelism? definitely.
>   Elegant tool for expressing everything else? definitely not.
These two lines sum up OCCAM.


>   (2) I fail to see the advantage of having no operator hierarchy or default 
>       data types:
>
>       why write this:
>
>	  (1.0 (REAL32) + (2.0 (REAL32) * 3.0 (REAL32))) - 4.0 (REAL32)
>
>       and count brackets when all I'm trying to do is:
>
>	  1.0 + 2.0*3.0 - 4.0
I think OCCAM is trying to make you aware of exactly what you are
doing numerically, although the use of brackets in the syntax is
confussing.
In ANSI C you also need 1.0f + 2.0f*3.0f - 4.0f to make things clear.
I think a lot of traditional C code ends up with additional type
conversion code produced that the user doesn't see; execpt that it
effect performance. Norcroft's ANSI C is very strong on this with its
'lower precission in wider context' and related warnings.

Thats enougth of me being nice to OCCAM for now. I better stop now
before I think of something to complain about.

--
Michael Stevens, Robotics Research Group,Dept of Engineering Science,Oxford,UK
INTERNET: michael@robots.oxford.ac.uk