Mailinglist Archive: yast-devel (177 mails)

< Previous Next >
Re: [yast-devel] Direction of YaST Architecture?
On Tue, Feb 01, 2011 at 12:48:57PM +0100, Josef Reidinger wrote:

Maybe it could be interesting to define our requirements on language. from my
POV it should:
1) be easy testable
2) high-level ( in general we don't care about programming language
performance as we do many time consuming tasks and if we need good
performance in some part then use bindings (see below))
3) easy debugging (it is really annoying debug ycp via debugger)
4) easy profiling (it is hard to find bottle neck)
5) easy bind libraries, especially in C and C++
6) object oriented with exception ( it is related to 2 as it would be great
if we can easy share object ( now we share functions and global variables and
it is sometime really pain. Exception is good for error handling. It e.g.
allow easy decide if error is from user or programmer and allow proper error
7) have at least medium community and codebase so we are not alone to
maintain it or be one of two maintainers
8) be enough mature, so we don't need to fight with language
9) allow easy sharing code like python eggs, ruby gem or perl cpan so we can
share our work where it make sense and have more users ( or easy use same
code also in other our products - just try remember if other our product use
any code written in YCP)

10) Small runtime environment for installation medium.

11) "Good" licence.

12) Allow to reduce module dependencies. E.g. in YCP if an
"import" fails the program terminates. In Python it is
possible to use "try import" and simply reduce the
functionality at runtime.

ciao Arvin

Arvin Schnell, <aschnell@xxxxxxx>
Senior Software Engineer, Research & Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
List Navigation
This Thread
Follow Ups