[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: python, then C++, or C++ from the start?

also sprach Oleg Verych <olecom@flower.upol.cz> [2007.05.31.0011 +0200]:
> Configuration of interfaces (hardware or software) is part of OS
> setup and proper operation. And this task must be solved on the
> principle basis, rather than jet-another-lang-flame. Once you have
> all kernel/network-interfaces (ioctl, sysctl, dhcp clients, etc.)
> realizations, why not just to start glue them? It's C/shell (or
> even C/SLang) ifs-glue thing, as you've wrote in the wiki page and
> not C++/python. IMHO it's far too away from ordinary application
> programming.

While I fundamentally agree with you, shell is also a major PITA and
there are even more pitfalls than with C. Add to that a lack of
proper debugging tools and you'll understand my tendency for a real

I should clarify that I am looking only at the core daemon right
now, and maybe the configuration/policy parser. The methods, which
are the actual workers doing the configuring will most certainly be
implemented in shell.

Please do not send copies of list mail to me; I read the list!
 .''`.   martin f. krafft <madduck@debian.org>
: :'  :  proud Debian developer, author, administrator, and user
`. `'`   http://people.debian.org/~madduck - http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
after you install windows xp, you have the option to create user
accounts. if you create user accounts, by default, they will have an
account type of administrator with no password. way to go!

Attachment: signature.asc
Description: Digital signature (GPG/PGP)

Reply to: