Naming sheme from moc output

[Jarosław Staniek]

Christian Ehrlicher said the following, On 2005-10-20 21:14:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello once again,
> 
> I've a question about the moc naming sheme. Why is it different to qmake?
> Qt/qmake:
> moc file.h -> moc_file.cpp
> moc file.cpp -> file.moc
> 
> Kde/bksys/automake
> moc file.h -> file.moc
> moc file.cpp -> file_moc.cpp
> 
> I don't think that it is good to create different filenames than Qt
> because it can confuse some people which come from Qt to Kde (like me).

I don't remember what was original reason to use .moc extension, but moc_*.cpp 
is not very easy to identify as generated (nto editable) file, while *.moc is.
Even using qmake in kdelibs3/win32 I didn't changed this behaviour but used 
kmoc script instead.

> 
> Christian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFDV+yPnNKwkgf+zVMRArACAJ9YxLri+En5ixgNeXGWY+TMynrzzQCfYMxx
> KuwVpLOfeOjXkqtzmZiUz3g=
> =eZZP
> -----END PGP SIGNATURE-----
> _______________________________________________
> Kde-buildsystem mailing list
> Kde-buildsystem at kde.org
> https://mail.kde.org/mailman/listinfo/kde-buildsystem
> 


-- 
regards / pozdrawiam,
  Jaroslaw Staniek / OpenOffice Polska
  Kexi Developer:
      http://www.kexi-project.org | http://koffice.org/kexi
  KDE3, KDE4 libraries for developing MS Windows applications:
      http://wiki.kde.org/tiki-index.php?page=KDElibs+for+win32