Organization & Recommendations

La issue propone un layout di arrayfire-lisp.asd con file in examples/ e src/, oltre a cl-autowrap-generated specs, ma non seleziona una modifica concreta. Leggi prima l’albero del repository e il README, poi conferma la struttura delle directory e l’approccio ai binding preferiti dal maintainer; il lavoro è completato solo quando quella direzione è concordata e viene definita un’attività specifica.

Thanks for making this @pavanky I've forked the repo and since there is no other way for me to communicate with you or the other people who are watching this repo (Hi @umar456 and @shehzan10 ) I figured I'd open an issue and start there.

I don't know how much experience you or the other ppl have w/ Common Lisp, so I'll assume the answer is "very little" and if I'm wrong... then no harm done. I typically use a directory structure like the following for most projects:

arrayfire-lisp
|- arrayfire-lisp.asd
|- Readme.md
|- ...
|- examples
|   `- examples.lisp
|- src
    |- package.lisp
    |- autowrap.lisp (if we're using cl-autowrap)
    |- ...
    `- spec
      |- arrayfire.h (a header we write to make autowrap generation easier)
      `- *.spec (the autowrap-generated spec files)

For the most part, if we use cl-autowrap and the C API of ArrayFire it should make life easier & faster. cl-sdl2 uses cl-autowrap completely and the SDL library is pretty extensive. I don't have any experience with the C portions of ArrayFire, but from looking at the docs, it looks pretty close.

As for style of the code, I try and stick to the Google CL Style Guide but that's just me (and I'm not a style nazi... unless you're using tabs & spaces for indentation!!!)

If you want me to set the groundwork on directory structure & whatnot that's cool. Just let me know which direction I should take, or if you have questions let me know & I'll try to answer them.