$FILES is for multipart-form data.
There's also a different method of uploading data, which is basically a POST to the URL with binary data, in which case use $BINARY.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts Menu
(define-macro (define-smacro)
(let (_temp1 (append (fn-macro) (cons (1 (args 0)) (rest $args))) _temp2 (args 0 0))
(def-new '_temp1 (sym _temp2 _temp2))
)
)
Thank you very much for sharing, I'll check it out.Quote from: "vlad lorenzo"
Up to now my impression is that the approach of xml to name-spaces is provably the most effective one:
Using a URL to define a unique global name-space and a symbol that references it as a prefix to cut down on the verbosity.
e.g.: in the module file:
(context 'example.com/library-name/module-name)
; code...
(context)
in the MAIN file:
; since (context) is the las evaluated expression it can be assigned to a symbol
(define xx (load "/home/vlad/newlisp/example.com/library-name/module-name.lsp"))
I thought of creating a library to add more features, but adding another dependency creates a barrier to sharing code.
i.e.: if every developer has his own unique way of managing name-spaces interoperability tends to suffer.
But I'll check out your library before settling on this.
* creating anonymous contexts to pass around as references without name clashes. (I still haven't looking into FOOP, so there might be a solution there)Quote
(ns-import 'com.example.*)
(ns-import 'com.example2.Test)
(Test:foo "bar")
So it looks like bothQuote from: "m i c h a e l"setqand setfare faster than set. I ran these tests multiple times, and the qand fversions are consistently faster. Lutz, should we be using setqin place of setfor the slight speed increase?