Argument names and types in API functions

[dfdx]

It turns out that currently all low-level functions (e.g. clblasSaxpy) have neither names, nor types of variables, e.g.:

julia> methods(clblasSaxpy)
clblasSaxpy(::Any, ::Any, ::Any, ::Any, ::Any, ::Any, ::Any, ::Any, ::Array{OpenCL.CmdQueue,1})
....

which makes it pretty hard to inspect and call such functions. This PR is an attempt to provide new low-level API with all the same functionality, but improved function signatures, e.g.:

clblasSaxpy(n::UInt64, alpha::Float32, X::Ptr{Void}, offx::UInt64, incx::Int32, Y::Ptr{Void}, offy::UInt64, incy::Int32, inQueues::Array{OpenCL.CmdQueue,1})

Here's is a lost of planned tasks that I'm going to follow if nobody has objections/suggestions:

• Implement @blasfun and @blasfun2 similar to @blas_func and @blas_func, but with argument names and types
• Translate L1 functions
• Translate L2 functions
• Translate L3 functions

The next step (probably, as a separate PR) will be to create high-level API, wrapping this one and using cl.CLArray instead of plain buffers.

Discussion is welcome.

[dfdx]

All functions are now translated to the new API (with proper argument names and types). I left old definitions for a couple of functions since future-based variants were implemented over them (e.g. see SCAL). Not sure if somebody is using it, please let me know if you do.

Since this PR doesn't introduce anything new and only improves existing functionality, I'll keep it here for one more week and merge myself if no one objects.

[jakebolewski]

@dfdx thanks!. As you see the current implementation was the first pass / bare amount of functionality implemented to be useful. All your improvements are reasonable, so I would just run with things for the time being and not wait on review.