wvxvw wrote:So, for example, if the project is supposed to compile to binaries, I'd have to have a build script, what are the conventions? Do I have to add a .make file? Shell scripts?
wvxvw wrote:When installing with asdf-install I remember that some libraries provided a way to test them immediately after they are installed - I think this is a very good idea, but how would I do that?
wvxvw wrote:How much documentation is considered *good enough*?
wvxvw wrote:Is there a documentation compiler (a program that would collect variables, functions, classes etc and their documentations and produce HTML / man / info / whatever other format)?
wvxvw wrote:Is there an example project, you could point finger and tell it's just as everyone would expect a normal CL project to be? (at googlecode / github)
wvxvw wrote: I see that quite often even if the form has special place for documentation (like defclass / defgeneric etc.) people choose to put documentation in the source file itself, not into the declaration - why would anyone do it one way and not another?
wvxvw wrote: but I've no idea how to comment a macro
wvxvw wrote:if you are using several reader macros, but you are using them exclusively in one file, but not another, would you put all macros in one file, regardless they aren't used together, but simply based on the fact they are all macros that modify the way the code is interpreted, or you would put the macro definition next to where it used?
Users browsing this forum: Bing [Bot], Google [Bot] and 2 guests