Re: Is stork a troll? (was Re: Trolltech QT license question)



On 2006-03-08, stork <stork@xxxxxxxxxxxx> wrote:
Stork replied to:

Thought experiment: If you have the [uncopyrightable] link tables and
function prototypes in hand,
I FALSIFIED THE ORIGINAL TEXT TO SAY "copyrightable" KEKEKEKE

Attribute my text and do not edit it.

What makes them copyrightable? I'm not talking about macros and inline
functions in the header, just the FACT that there is a function called
"foo" which takes some parameters and returns some type, or for the link
table, the fact that a symbol exists by the name "foo" at all. No more
copyrightable than a phone book.
.



Relevant Pages

  • Re: What is the gain of "inline"
    ...  This is presumably because "static inline" functions are ... Inline functions MUST be written in header files... ... Inline functions provide safety over macros. ...
    (comp.lang.c)
  • Re: What is the gain of "inline"
    ... which is about comparing macros with inline functions.. ... but macros also don't affect compilation speed as much as ... + header class definitions, templates, etc.  At the point where you ...
    (comp.lang.c)
  • Re: Lisp semantics vs. Mathematica semantics
    ... Macros are expanded before run-time so they provide partial specialisation. ... (list 'foo 'bar bar)) ... Another important distinction between macros in Lisp and macros in OCaml is that whilst both Lisp macros and campl4 can perform arbitrary transformations upon ASTs of their respective languages, Lisp macros produce Lisp whilst campl4 macros produce OCaml. ...
    (comp.lang.lisp)
  • Re: CLOS and databases
    ... > define macros that can use type information (something that Common ... in my interpreter I've used the Java bean conventions to map accessors, ... It only tries getFoo() and isFooif foois undefined. ... either the handler for the signalling thread is null or the no handler ...
    (comp.lang.lisp)
  • Re: At long last, first release of Lexicon code
    ... way to get my ^FOO syntax working well enough to get my new macro system ... results is a Lisp-1 without hygienic macros but with an operational ... (lst lst lst) ... That is because the lexicon code heavily munges the behavior ...
    (comp.lang.lisp)