Re: Symbol clashes: how to avoid them. Part 2

On Fri, 31 Oct 2008 13:51:30 -0700, budden wrote:

Currently I am working under rather simple task: replace TADODataset to
TexADODataset in a Delphi app (lexical analysys of .pas and .dfm and
accurate replacement of words, parsing "uses" statements and replacing
lists of units used. Would earn some money.

Is it enough or I should work 3 months more?

No, apparently you didn't gain anything in the past, so it is not likely
to happen. The other day we had someone who claimed he has been learning
Lisp for 3 years but it didn't show.

(BTW, I'm looking for a lisp job all the time, but unable to find one.

I wonder why. With the great language design skills you have
demonstrated here, employees should be bidding for you like crazy.

(defun analyze-statistic (statistics &option (type 'total))
(let* ((statistic (slot-value statistics type) ;;

First of all, you don't need to make this a slot. OO engine is
mistified, but it is very simple in its basic principle. Just arrays
with a named slots. Well for lisp they are hashes. You may use just an
array - it is exactly the same in terms of performance. E.g., in Delphi

You are missing the point. I care about performance, but I also care
about readability of my programs. Yes, I could reimplement objects with
hash tables, but I chose not to, because the language I am working in has
the ability to address slots even when they are not hardcoded, and I find
this convenient.

course, it outperforms python, perl, etc... As fast as Java, but much

Give me a break. Java bytecode doesn't come close to a decent Lisp
compiler.

removed from A (or no longer exported), and at the same time, a new
symbol B:FOO appears in B, also naming a function. No, I didn't overlook
it. But this event is rather improbable. If so, it is likely that A:FOO

How would you know what is improbable?

Your problem is a classical one: you are a Blub [1] programmer, so you
want Lisp to look/feel like Blub. You make clueless suggestions about
superficial features. I am not saying that Common Lisp cannot be
improved, but it is ever improved, it will not be done by those who make
trivial syntactic modifications that would make crucial language features
(like macros) harder if not impossible and the whole language
inconsistent.

Tamas

[1] http://www.paulgraham.com/avg.html
.

Relevant Pages

  • Re: ILC2005: McCarthy denounces Common Lisp, "Lisp", XML, and Rahul
    ... >> the language should be available to users. ... In the design of Common Lisp, I asked Dave Moon (one of the architects ... Now, there are good kinds of low-level, like the way that floats are ...
    (comp.lang.lisp)
  • Re: CollabRx seeks brilliant engineers for an excellent e-science adventure
    ... belief that lisp programmers are smarter/better. ... Java or PHP programmers. ... a type of language that attracts a personality that meets my perceptions ...
    (comp.lang.lisp)
  • Re: Whats the best language to learn...
    ... on processors designed to run Lisp and Lisp OSes. ... byte-addressed memory, has native support for variable-sized value types, ... popular OO language, rather a language about like that of Delphi would have ... lisp, java, ruby, etc. ...
    (comp.programming)
  • Re: Program compression
    ... TM> supported by your favorite language (LISP) are good concepts. ... then call the Java compiler to compile that source file to a Class ... TM-STC> Since static type checking makes run-time type checks unnecessary, ...
    (comp.programming)
  • Re: Is anybodys favorite computer programming language not included here?
    ... to talk about getting me some paying work writing Java classes. ... and could be copied to a script (as in Java BeanShell or Lisp PROG). ... >> please post a followup saying what language it is, ... Server: "Mother, ...
    (comp.programming)