From: Paul Davis <paul@linuxaudiosystems.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Joern Nettingsmeier <nettings@folkwang-hochschule.de>,
Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Re: future ALSA development
Date: Tue, 24 Jun 2003 08:16:18 -0400 [thread overview]
Message-ID: <200306241209.OAA28971@alsa.alsa-project.org> (raw)
In-Reply-To: Your message of "Tue, 24 Jun 2003 13:56:48 +0200." <Pine.LNX.4.44.0306241352410.1838-100000@pnote.perex-int.cz>
>There are two differences between lisp and alsa configuration language.
>Lisp is standard dynamic language but the ALSA configuration is static
>(if you ommit the runtime evaluation hacks added to enhance functinality).
but the runtime evaluation hacks are precisely what give rise to the
problems. you and abramo may have conceived of it as a static language
in the first place, but it clearly has, along with just about every other
"small language", mutated into something else. the story of PHP is one
of the more recent illustrations of this.
>It is something similar like "HTML" and "Java script". The first one is
>good to describe the static part of web pages, but if you want something
>dynamic, you have to use another embeded language.
or use a real language for the whole thing. this is not the web. there
is no reason to use a few lines of static container code (e.g. HTML)
to wrap a real programming language (e.g. Java).
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
next prev parent reply other threads:[~2003-06-24 12:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 19:10 future ALSA development Jaroslav Kysela
2003-06-23 11:14 ` Takashi Iwai
2003-06-23 12:01 ` Jaroslav Kysela
2003-06-23 13:13 ` Takashi Iwai
2003-06-23 13:41 ` Paul Davis
2003-06-23 13:51 ` Takashi Iwai
2003-06-23 14:18 ` Paul Davis
2003-06-23 22:22 ` Joern Nettingsmeier
2003-06-24 7:51 ` mru
2003-06-24 8:14 ` Jaroslav Kysela
2003-06-24 11:19 ` Abramo Bagnara
2003-06-24 11:43 ` Paul Davis
2003-06-24 11:56 ` Jaroslav Kysela
2003-06-24 12:16 ` Paul Davis [this message]
2003-06-24 17:11 ` Takashi Iwai
2003-06-24 18:28 ` Jaroslav Kysela
2003-06-25 17:49 ` PCMCIA In Kernel Or In ALSA Driver? Len Moskowitz
2003-06-25 18:51 ` Jaroslav Kysela
2003-06-30 10:17 ` future ALSA development Takashi Iwai
2003-06-24 8:28 ` iriXx
2003-07-03 13:39 ` Kai Vehmanen
2003-07-07 11:26 ` Takashi Iwai
2003-10-01 9:37 ` ALSA in embedded use (was: Re: future ALSA development) Kai Vehmanen
2003-10-01 13:13 ` Takashi Iwai
2003-06-24 12:52 ` future ALSA development Giuliano Pochini
2003-06-24 13:04 ` Jaroslav Kysela
2003-06-24 17:12 ` Takashi Iwai
2003-07-03 14:21 ` Kai Vehmanen
2003-07-03 14:36 ` Kai Vehmanen
2003-07-03 16:05 ` Thomas Charbonnel
2003-07-07 11:37 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200306241209.OAA28971@alsa.alsa-project.org \
--to=paul@linuxaudiosystems.com \
--cc=alsa-devel@alsa-project.org \
--cc=nettings@folkwang-hochschule.de \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.