Dave Dunn wrote:
> 
> Warp wrote:
> 
> >   Why it would be more elegant?
> >   And FYI, this will be a standard macro in 3.5.
> 
> To your second point first, this is great news. Not having seen the beta, like
> a lot of other people, I can only guess what macros are included. I was
> thinking of elegance in terms of simplicity of use for the end user, not in
> the sense that programmers sometimes use it. It seemed to me that an internal
> keyword, based on point_at or look_at would simply be more intuitive while
> coding than having to invoke a macro. But hey, I'll take the macro, gladly.  :
> )

The beauty of the standard macro collection is that you simply include the
file and the functions act just like built in keywords. They are basically
transparent to the user and offer the added benifit that if the function
does not work as you want it to you modify it until it does. That is
something you cannot do with built in features :)

-- 
Ken Tyler

Post a reply to this message