Re: Exception Misconceptions
In article <33f73097-702a-478f-97a0-4d2e74b280c6@a21g2000yqc.googlegroups.com>, James Kanze <james.kanze@gmail.com> wrote:
On 20 Dec, 10:16, ta...@mongo.net (tanix) wrote:
In article <hgkcfk$1kg...@news.ett.com.ua>, "Balog Pal"
<p...@lib.hu> wrote:
"tanix" <ta...@mongo.net>
Ok, the situation is this:
[whole story can be replaced with "you have to keep info on
arbitrary number of incoming network packets for arbitrary
long time"]
I know, I know. I had to deal with one liner mentality for
quite a while.
But you see, if you write these one liners, you are basically
dealing with bio robots.
There is no fun of a story in one liners.
That is why I suggested on other thread that before you get
into programming, first learn about beauty. Then learn about
music. And ONLY THEN we are going to have any luck talking to
people like you.
Well, I find his version more beautiful than yours. It's
obviously not complete, but it does sum up the issues for one
part of the application in a very clear and concise manner.
(And as my high school English teacher used to say: "Good
writing is clear and concise.")
I do not happen to communicate in one liners of a type "coca
cola is good. drink coca cola". Because I perceive it as
programming instructions for zombies and biorobots.
Do you mind?
Yes. You seem to prefer long, drawn out descriptions which jump
back and forth between issues. That's not what I'd consider
good writing.
Too bad.
Not interested.
Cya.
Note that I'm not saying that such things shouldn't occur. But
you're description sounded like a first brainstorming session,
when you really don't know yet what the application should do.
Balog's is, of course, too simple, in that it only addresses one
aspect of the problem. But he has gotten over the first design
issue: breaking the problem up into simpler problems, which can
each be addressed by a simple statement.
My first reaction to your description is that you obviously need
two processes: one doing the filtering, and another to manage
the GUI. With a queue between them. In this case, from
experience, I'd say that two processes are a must, because you
want the filtering to maintain as small a footprint and use as
few resources as possible. Which means, BTW, that I would do it
in C++, and that I wouldn't use garbage collection, since
garbage collection does have a significant memory overhead (and
in such filtering applications, unlike a lot of other
applications, doesn't really buy you that much). For the GUI,
I'd use Java, because I know Swing, and I don't know any of the
C++ GUI libraries.
For the queue itself, I'd try to use something provided by the
system, because writing robust and rapid queue management in
Java is a pain. (You need to access system services to do it
efficiently.) Lacking something in the system, I'd write the
queue management in C++, and use JNI to interface with it on the
Java side.
--
Programmer's Goldmine collections:
http://preciseinfo.org
Tens of thousands of code examples and expert discussions on
C++, MFC, VC, ATL, STL, templates, Java, Python, Javascript,
organized by major topics of language, tools, methods, techniques.