--nextPart1642980.Bo7ubFpEhA
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 14 June 2005 14:27, Alexander Neundorf wrote:
> On Tuesday 14 June 2005 09:28, Stephan Kulow wrote:
> > Am Montag 13 Juni 2005 20:07 schrieb Alexander Neundorf:
> > > Ok, here my take on cmake. I'm no expert in linking issues, so I can't
> > > comment on everything.
> >
> > Call me stubborn, but I won't touch cmake syntax.
>
> Probably because the commands are all upper case and it has a feature
> called "macro" and macros are evil in C++ ?
> Honestly, if you'd have any valid argument it would be ok, but just stati=
ng
> that you don't like the look is no real argument.

Well, but it is.  Now I'm hardly one to say that Python is the best syntax =
in=20
the world (because it's not), but although 'look' isn't the end-all-be-all,=
 I=20
would hope that it would be a factor.  Now that so many people are accustom=
ed=20
to Netiquette it seems odd to use a build system WHERE EVERYTHING IS=20
UPPERCASED LIKE A 1968 IBM MAINFRAME. ;)

Of course if something nicer looking didn't have a feature we'd need then w=
e=20
wouldn't have a choice, but I think that if we're making the switch we migh=
t=20
as well have our cake and eat it too.

> Now seriously, there can be no "complete solution" which supports building
> KDE 3 (4) out of the box (except unsermake which was written for exactly
> this purpose). You can't expect that a buildsystem without special
> adaptation for KDE knows how to handle e.g. a foo.kcfgc.

Well I don't think that we can seriously expect to pick a system that needs=
 no=20
adaptation.  And from what I can tell we'll probably have to replace autoco=
nf=20
ourselves.  But I wouldn't worry about a build system not supporting=20
KDE-specific things like .kcfgc as long as it can be easily added by us.

> > And if I can pick incomplete solutions, I will avoid the ones
> > with the uglier syntax.
>
> Ugliness is a matter of taste.
=46air enough.  But I think most would agree that all uppercase isn't exact=
ly=20
the easiest on the eyes.

Regards,
 - Michael Pyne

--nextPart1642980.Bo7ubFpEhA
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCr3FnqjQYp5Omm0oRApMIAJ9t9C1M+C6/tWwSXspOSy0cATWQLgCdFLhM
qrvJt/D+PUpDKVoJt61SCeY=
=g0rY
-----END PGP SIGNATURE-----

--nextPart1642980.Bo7ubFpEhA--