L
Lew
Paul said:Has Pascal gotten that much better at UI design since then (assuming the
had UIs)?
Portuguese is a better language than English.
Paul said:Has Pascal gotten that much better at UI design since then (assuming the
had UIs)?
Pascal said:Series Expansion said:You did? What was it, the bozo of the week award? Can I see it? Pretty
please?
No, now it will just make all your coworkers break out in hives when
your code is checked into the source code repository and a big
whirling red light and wailing Klaxon promptly pop out of panels on
the git server box to warn of an impending meltdown.
Not at all. This is done every days by lisp programmers and no such
thing occurs.
But they're just as obsolete. If nothing else, their user interfaces
will be woefully subpar by modern standards.
You are not the one to say whether they'd be obsolete or not, only
their users.
And corporations may have something else to do, and something else to
finance, than to pay java [sic] programmers to follow the fashion of the day
in GUI for their mission critical software.
Series said:Ignoring the spurious NIL here, have you forgotten a) Turing
completeness and b) java.math.BigInteger?
Series said:Says someone who evidently has never heard of junit [sic].
Pillsy said:It's an awfully good thing that Common Lisp didn't do that, then,
isn't it?
Series said:Says someone who evidently has never heard of junit [sic].
Alessio said:I know JUnit and regularly use it - for testing Java code. I'm not
aware of how JUnit could test fragments of XML.
Pillsy said:But it doesn't adhere to the Lisp restriction that macros respect
namespaces. Nor can you just redefine either standard functions or
standard macros.
C macros makes it easy to do things that are awful and useless, like
your example, and doing non-trivial useful things is usually very
difficult and very error-prone.
gugamilare said:Oh, he was talking about my English. Ok, I might have made English
mistakes throughout the thread, I am not a native English speaker so
understand that writing things in English is not as intuitive and as
easy as it is to you, even though I am not bad in English. If you
think I am stupid just because my English is not as good as yours, you
don't have a point.
Paul said:You might want to explain this "lack of encapsulation barrier" stuff so
we can tell you specifically how wrong you are this time.
Pascal said:We have priority on the terminology here.
gugamilare said:ConteXt, before you flame me again for writing wrong English.
Pascal said:Because we're talking about lisp macros and they have nothing in common with C macros.
gugamilare said:He meant that a C macro is so much different from a Lisp macro that,
to understand a Lisp macro, you need not to take any knowledge you
already have using C macros.
That would explain why his postings read like something out of those
"Top 10 Silly Myths About Lisp" articles.
Oh well. IHBT, IHL, et c.
Pascal said:I'll try a last time. You've been explained that the macro can and
will generate unique name, that in no way may be collided. This is
absolutely impossible.
And now for the "personal insult":
Go learn Common Lisp! Or even Scheme with its hygienic macros, you
might like them better than Common Lisp macros.
Jussi Piitulainen said:Googling for Emacs and Slime, the first hit I got was this page:
<http://common-lisp.net/project/slime/>. The page is short and to the
point, and it begins with a description and feature highlights.
There is a screenshot of a window that seems to match Adlai's
description, more or less. A link to a long QuickTime movie is dead,
Series said:It's a text editor. A text editor won't know Lisp source from Java
source, or either from a letter to Grandma.
I am not trolling. Lispers fired the first shots in this little teapot-
tempest, and Lispers have already done a lot of complaining abou Java
here. We have responded in kind, some of us, while others have
attempted a more reasoned debate about the merits, to no avail.
I don't know if anyone here is trolling,
aside from the OP with his umpteenth joblessness whine, to be honest.
I said:Nobody's talking about a terminal-oriented editor. They're talking about
Emacs, which has been a window-based application since the mid-1980s.
Nobody's talking about a curses-based unix editor from the seventies.
They're talking about Emacs, which is a working modern GUI program with
multiple overlapping windows and menus.
gugamilare said:This is the thing: I am not in c.l.j.p, I am in comp.lang.lisp, where
these posts where originated and therefore where they belong. Someone
just moved them to c.l.j.p for whatever reason, but this was initially
a c.l.l post.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.