Re: C++ framework design
On 3/22/2013 1:52 PM, Jorgen Grahn wrote:
On Fri, 2013-03-22, Victor Bazarov wrote:
On 3/22/2013 10:11 AM, Jorgen Grahn wrote:
On Fri, 2013-03-22, Ian Collins wrote:
Chicken McNuggets wrote:
Hi,
I'm working on a C++ web framework as a hobby project and am looking for
some advice on the best way to design it.
Currently my plan is the following:
...
You don't say what the purpose of your framework is.
Put differently: IMO it's suicide to design a framework or an API
without at the same time designing at least one non-toy, real
application which uses it.
"Suicide"? It can be a waste of time. It can be laden with
frustration. It can mean more work later (re-working and re-designing
is often more laborious than doing it correctly from scratch). But
"suicide"? Come on!...
It should be obvious that I didn't mean that literally, right?
Well, yes, *that* was obvious. Suicide *literally* means death, and
unless the OP somehow is engaged in writing software for life-supporting
medical apparatus and is preparing to self-test it without even a trial
run under a debugger, would be *literally* suicide. Everything else it
not *literally* suicide, it's only *figuratively* suicide.
But then I don't agree with that, still. Writing API without a clear
specification in front of you (provided by that "real application which
uses it") is not even *figuratively* suicide. Sticking one's foot into
the adjacent public bathroom stall, as we know, is a political suicide
in a *figurative* sense. Betting your life savings on a horse known to
lose every race would be a suicide (in financial sense, and again,
figuratively). Writing an API? Really??
V
--
I do not respond to top-posted replies, please don't ask