If you have people making messy spreadsheets that are
hard to maintain, you might want to look at this. I have
not used it myself:
http://www.modelsheetsoft.com
But it's from Howard Cannon, Symbolics co-founder and
main inventor of Flavors, an ancestor of CLOS.
-- Dan
On Fri, Jul 22, 2011 at 9
This is a video about "LISP Technology at Cisco".
http://www.youtube.com/watch?v=JIiBMZ86jZo&feature=player_embedded
(It has nothing to do with Lisp, either.)
:)
-- Dan
___
pro mailing list
pro@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mail
And if you ever wondered why CLOS makes you spell
out the names of readers and accessors, this is why.
CLOS does not want to make any assumptions about
how you want to make decisions about what
packages things are in.
It's the "right thing" rather than the "worse is better"
way, with all the usual
Could you tell me where to find that? Thanks. -- Dan
On Tue, Jun 14, 2011 at 3:50 AM, Alessio Stalla wrote:
> On Tue, Jun 14, 2011 at 9:37 AM, Marco Antoniotti
> wrote:
> >
> > On Jun 13, 2011, at 21:18 , Daniel Weinreb wrote:
> >
> >> Friends,
> >>
&g
package prefixes, so the dictionary- isn't there.
Anyway, I'll take a look at what you wrote. Thanks again.
-- Dan
On Mon, Jun 13, 2011 at 9:52 PM, Pascal J. Bourguignon <
p...@informatimago.com> wrote:
> Daniel Weinreb writes:
>
> > Friends,
> >
> >
Oh, yes, thank you very much for bringing up the issue of threads!
I have to mention that they are not thread-safe. The CL definition does not
say whether hash tables are thread-safe since the CL definition has no
thread concept. CCL hash tables are thread-safe.
Right now, they aren't CLOS inst
Friends,
I wrote a little package for "fash hash tables", which provide an
abstraction that is analogous to that of Common Lisp hash tables, but
is faster for tables with few elements, and only slightly inferior for
tables with many elements.
I did this because performance analysis showed that ou
I, myself, really dislike &aux. It has been so long
since I have seen it that I have forgotten that
it even exists. We never use it; and I should
add that to our style guide.
I don't even like
(let (a b c) ...)
since I prefer to think of "let" in the Scheme sense
of "I am naming the result of
If you are ever in the need of creating PHP code,
take a look at this:
http://scriptor.github.com/pharen/index.html
-- Dan
___
pro mailing list
pro@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mailman/listinfo/pro
We had to take the talk down for reasons that I
think were kind of stupid and would rather not
go into.
Also, I don't feel that the talk was a good one.
I did not prepare for it, thinking that I could
do it on the fly, but I was wrong. I should
have done preparation. So the information
was rath
In large Lisp systems, it's easy to run into problems with
the order in which files are loaded and compiled.
One often-vexing issue is where to put package
declarations. If a file names an exported symbol
such as foo:bar, the package foo with its
export list must have been loaded earlier.
In gen
Has anybody written a domain-specific-language
set of macros (or functions) to provide "awk"
functionality from Common Lisp, with roughly
the kind of brevity that awk users like?
-- Dan
___
pro mailing list
pro@common-lisp.net
http://common-lisp.net/cg
So the next time anyone says that there aren't any
libraries for Common Lisp, we can reply that
there are so many good parser libraries that
one must compare notes to figure out which is
best for which situation. So there, ye of little
faith! :)
-- Dan
Scott L. Burson wrote:
On Thu, Feb 3, 20
Raffael Cavallaro wrote:
On Feb 3, 2011, at 8:05 AM, Steve Haflich wrote:
My favorite critter to represent has always been the Lambasaurus Rex.
It might be risky to associate lisp with both a dinosaur, and an outdated interpretation of how that dinosaur looked in life
Indeed, the
Didier Verna wrote:
Daniel Weinreb wrote:
Yes, we use it heavily, mainly for date/time processing, which can be
very complicated when you're dealing with time zones and such.
Example:
(list :departure-time (format nil "~/zul%ISO8601/" departure-time-zul)
OK, but
There appears to be a new trend of putting cute
animals on your HTTP 404 page. Twitter has
a "Fail Whale", and now Tumblr has "TumblBeasts":
http://www.observer.com/2011/tech/tumblr-adds-oatmeals-suggested-tumbeasts-404-page
Perhaps we can have an easy way to make Lisp-based
web sites use the "p
Oh, sorry; right, it's just for convenience to put
them in cl-user, to keep the format strings short.
Edi Weitz wrote:
On Tue, Jan 25, 2011 at 6:36 PM, Daniel Weinreb wrote:
I actually can't remember why package prefixes
aren't allowed. It was a long time ago.
T
Didier Verna wrote:
> I'm aware of the ~// construct, which I find extremely cumbersome. Does
> anybody actually use it?
Yes, we use it heavily, mainly for date/time processing,
which can be very complicated when you're dealing
with time zones and such. Example:
(list :depa
On 1/21/11 6:01 AM, Svante Carl v. Erichsen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi!
>
> I should call it string-conc, conc-string, or conc->string. I should
> not expect from first sight that either, string+ or string*, would
> concatenate. From those names, it also would
Correction:
Daniel Weinreb wrote:
>
> As for me, if the Google acquisition of ITA happens, chances
> are that I won't be allowed to use Common Lisp,
Sorry, what I meant was that it was unlikely
that we'd be able to use Common Lisp for
NEW projects. I am confident that Google
i
Alexander,
Here's my own interpretation of what Drew said, which I admit
may or may not be what he had in mind. (I do agree that he
said it in a rude way.) The heart of what he wrote is:
>>
>> And i'm not convinced a mailing list for professional lisp developers
>> needs more diatribes explainin
Alexander Repenning wrote:
> is still mostly true but as I am tracking the speed of JavaScript
> versus Common Lisp I can see a scary performance cross over point in
> the near future (months). Already, in some of our benchmarks
> JavaScript running in OS X Chrome is getting very close (10% ga
This is a very nice essay to help people get over their
initial problems with Lisp:
http://pavelpenev.posterous.com/learning-lisp-the-bump-free-way
I also just came across an online book called "Successful Lisp",
by David B. Lamkins (maybe many of you already know
about this):
http://psg.com/~dl
If you have a function that is a predicate, in the sense that
the function's contract says that its value should be interpreted
as being either false or true, do you think it's better to code
it so that it always returns "t" for the true case?
Since Common Lisp is quite clear that when a value
is
18:03, Didier Verna wrote:
Daniel Weinreb wrote:
This conversation has been good.
Yup. Here's what I gather from it, mostly:
- a shared slot's initform is required to be evaluated when the class is
created,
I agree here.
- however, nothing tells us th
Daniel Weinreb wrote:
This conversation has been good. I agree with both Svante
and Scott.
As is often the case with the spec, it is not quite unambiguous.
Oh, and I meant to say that I'm not sure the spec is 100%
clear on which forms are evaluated v. not evaluated, and
whether
This conversation has been good. I agree with both Svante
and Scott.
As is often the case with the spec, it is not quite unambiguous.
It seems to me that the spec is having trouble deciding whether
it is a real, strict, firm language spec, or a useful tutorial/reference
documentation aimed at wh
On 12/30/10 2:12 PM, Pascal Costanza wrote:
> The solution I proposed last avoids that by having exactly one class
> definition. However, such cases are unlikely to occur in practice, so
> this is likely just an academic exercise. Nevertheless, I think it's
> important to mention this
I agree th
Yes, this kind of thing is essential if you want to
design a system that stays up.
I have another fun thing along these lines. When
you start a request that comes into the server,
you assign it an integer. As the handling of
the request reaches transaction boundaries
(transactions on an underly
Anton,
These are all very good questions. I'm going to try to
write up an essay about these topics suitable for
posting on my blog, since there's so much to say.
The use of packages that I have been advocating
here is not used a lot in practice in Common Lisp,
but the more I think about it, the
Scott McKay wrote:
On Dec 19, 2010, at 10:46 AM, Daniel Herring wrote:
On Sun, 19 Dec 2010, Scott McKay wrote:
On Dec 17, 2010, at 4:57 PM, aeri...@xs4all.nl wrote:
On 17 dec 2010, at 22:15, Eli Naeher wrote:
Right now I usually have (under screen) one instance of
Jack Harper wrote:
> ...an interesting idea.
>
> Years ago (1984), I had dinner with Nils Nilsson (AI pioneer) and he
> mentioned the idea that he wanted to build a system that once alive would
> never be powered down again - in his view a minor but necessary prerequisite
> of an AI system.
>
It depends on what you mean by "interact". Is it a program
interacting or a human interacting. If you mean the latter, then
Swank makes sense. If the former, Swank isn't needed and is probably
overkill As Sam Steingold says:
A less generic answer would be to start an extra thread which woul
Anton,
Thank you very much for your mail. It prompted me
to explain what I'm thinking of in a much more
clear (I hope!!) way. Here we go:
Anton Vodonosov wrote:
What is the difference
for modularity in case of subclassing, from other cases were we apply modularity?
I can't find the differen
Anton,
Thank you very much for your mail. It prompted me to explain what I'm
thinking of in a much more clear (I hope!!) way. Here we go:
Anton Vodonosov wrote:
> What is the difference
> for modularity in case of subclassing, from other cases were we apply
modularity?
> I can't find the d
It looks like we do not have a concensus. Thanks
to everybody for contributing!
-- Dan
___
pro mailing list
pro@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/pro
In case these terms are too old for anyone to know
them, we used to use the phrase "for effect" to
mean a function that was called for the sake
of its side-effects, versus "for value" when it was
called for the sake of its returned value. (Actually
I'm not sure I remember what we called a function
Faré wrote:
On 1 December 2010 10:25, Daniel Weinreb wrote:
Here is a way that CL sucks badly: protocols are not first-class entities.
To modify a protocol is something done to the source code *outside* of the
Lisp world. It cannot be done programmatically.
Adherence to the protocol
(This is a new topic.)
Many times, people have presented a major problem with object-oriented
programming as it is often/idiomatically used. The good thing is that
OOP, when done right (in Lisp, that means, among other things, always
using defgeneric explicitly), provides a great abstarct interfa
You considered the idea that when you write a library (internal
module, whatever) that defines a new type of Lisp object, it should
not necessarily be apparent to the caller whether the implementation
of objects of that type happen to use CLOS.
Hans: Of course, one may want to argue that DEFCL
Sorry for the delay; here are my comments.
Meta-point: I prefer to work out these issues by first disregarding
speed issues, and figuring out what the best semantics is. Then,
later, if there is real need for speedup, we can do that, but keep in
place the original intention of the code, for the
Anyone who wants to do it can find some starting
points in my lisp-survey paper.
Pascal Costanza wrote:
> Hi,
>
> Dan recently did a survey of existing Common Lisp implementations, which IMO
> is a very valuable resource. Another valuable resource would be an updated
> list of current existing p
Apologies, the auto-complete in Thunderbird seems
to have screwed the address here. Sorry!
Yakov Zaytsev wrote:
wtf
On Fri, Oct 29, 2010 at 7:23 PM, Daniel Weinreb <mailto:d...@itasoftware.com>> wrote:
Dennis Kucinich's race is very close. If you want him to win,
Dennis Kucinich's race is very close. If you want him to win, send $, see:
http://kucinich.us/index.php?option=com_content&task=view&id=46&Itemid=58
___
pro mailing list
pro@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/pro
44 matches
Mail list logo
