"…mais ce serait peut-être l'une des plus grandes opportunités manquées de notre époque si le logiciel libre ne libérait rien d'autre que du code…"

Archive for mars 2008

Des nouvelles de python : pycon2008, python 3000, jython, LINQ, concurrency, django

Posted by patrick sur mars 31, 2008

Après presque 3 semaines sans blogger, quelques nouvelles de Pycon 2008

http://www.python.org/doc/essays/ppt/pycon2008/Py3kAndYou.pdf (« Guido nous parle de Python 3000 dans un document de 21 pages. Quelques extraits: Why Py3k: “Open source needs to move or die”,What’s In It For You: More predictable Unicode handling, Makes “Python fits in your brain” more true, TOOWTDI (There’s Only One Way To Do It — The Zen of Python),  There are tools to help you switch!,  Don’t bother with the trivial stuff though:  The 2to3 tool will handle this, In 2.6:  Use bytes and b’…’ for all data,  Use unicode for all text, The Role of Python 2.6:  Many 3.0 features backported,  More volunteers needed! Transition Strategies:  Port to 2.6 first,  Using 2to3 whenever you can, Release Schedule:  The 3.0final release is now scheduled for September 3, 2008, Wrapping Up:  Have fun with the new features,  Enjoy fewer bugs, traps, surprises, Resources: http://docs.python.org/dev/3.0/whatsnew/3.0.html ,  PEPs: http://python.org/dev/peps/pep-3000/,  Subversion:  svn.python.org/view/python/branches/py3k/ )

http://www.artima.com/weblogs/viewpost.jsp?thread=227041 (« I’d like to take this opportunity to remind you of a really important issue that I neglected to mention in the talk: Don’t change your APIs incompatibly when porting to Py3k.
Yes, you heard that right: even though Python 3.0 is changing incompatibly, I implore you (especially if you’re maintaining a library that’s used by others) not to make incompatible changes to your API. If you have make API changes, do them before you port to 3.0 — release a version with the new API for Python 2.5, or 2.6 if you must. (Or do it later, after you’ve released a port to 3.0 without adding new features.
« )

http://www.sauria.com/blog/2008/03/20/pycon-2008/ (« …Raymond’s talk gives a cost model for the core containers, and having an understanding of that model is important for folks who are writing Python programs. It’s also useful for developers of alternate Python implementations because it allows them to follow suit or to diverge and (hopefully) document the places where the cost model is different. My next favorite talk was Jim Baker’s “More Iterators in Action”. I missed the talk given last year, but I liked this one. Jim hit two of my favorite topics, language integrated query (LINQ) (albeit without the DSL), and concurrency. There was a lot of interest in concurrency this year, which warms my heart, because I see high-level/dynamic languages and concurrency as the chocolate and peanut butter…If I was surprised about the jump in size of PyCon, I was even more surprised by the amount of energy around Jython. At most of the previous PyCon’s that I attended, people would mention Jython, and either be sorry that it was too out of date to consider, or be just plain dismissive of it. This year there was none of that. People were very interested in Jython. I was really surprised by how much interest there was, and by some of the people who were interested. It was certainly a nice feeling to sit in the sprint room and occasionally have people pop in to ask if such and such was running in Jython yet, or did Jython support X because package Y needed it…If I was surprised about the jump in size of PyCon, I was even more surprised by the amount of energy around Jython. At most of the previous PyCon’s that I attended, people would mention Jython, and either be sorry that it was too out of date to consider, or be just plain dismissive of it. This year there was none of that. People were very interested in Jython. I was really surprised by how much interest there was, and by some of the people who were interested. It was certainly a nice feeling to sit in the sprint room and occasionally have people pop in to ask if such and such was running in Jython yet, or did Jython support X because package Y needed it »)

http://nedbatchelder.com/blog/200803/pycon_2008_notes.html (« I got back from Pycon last night. I’d taken notes on all the sessions I attended. They’re kind of sketchy, and I don’t know if they’ll be of any use to anyone else, but I figured I’d put them up anyway. My apologies to speakers whom I have crudely paraphrased here. The quality of these notes varies as my energy level waxed and waned. »)

http://us.pycon.org/2008/conference/talks/

http://us.pycon.org/2008/conference/talks/?filter=django

http://us.pycon.org/2008/conference/talks/?filter=concurrency

http://us.pycon.org/2008/conference/talks/?filter=google%20spreadsheets

http://www.artima.com/weblogs/viewpost.jsp?thread=227496 (« I think I’ve been using Python for close to 12 years now, and it’s been my favorite language for much of that time (I’ve given 2 keynotes and one or two talks at the Python conferences. It’s by far my favorite language to consult in). Long enough to get used to the fact that people typically don’t get it (« Yes, I always indent my code like that anyway, but I could never use a language that REQUIRED it!…I’m not into Django myself; I’m more interested in the flexibility of the approach taken by TurboGears 2 (I just spent a significant amount of time cleaning up the TurboGears 2 Wiki Tutorial). However, I think the combination of choices offered by Django + TurboGears covers people’s needs better than a single monolithic approach, and Django appears to be the right solution for a large portion of the applications out there….Regarding Django: It’s great to see Django picking up so much steam. I’ve done a few Django projects and I’m really impressed by it. It really takes advantage of Python’s strenghts. Anybody thinking about creating a web application should check it out. Highly recommended.« )

Publicités

Posted in 2008, jython, python | Tagué: | Leave a Comment »

Migration vers le libre: sortie du livre « Changer pour OpenOffice.org »

Posted by patrick sur mars 11, 2008

Changer pour OpenOffice

Un grand nombre de gens ignore encore que leur coûteuse suite MS Office peut être avantageusement remplacée par OpenOffice.org. Le livre « Changer pour OpenOffice » leur permettra de franchir le pas.

OpenOffice

http://www.wikimindmap.org/viewmap.php?wiki=fr.wikipedia.org&topic=OpenOffice.org

Source: http://linuxfr.org/2008/03/06/23805.html

————————————————-8<——————————————————————–

Livre : Sortie du livre « Changer pour OpenOffice.org »
Posté par boogieplayer (page perso. Modéré le jeudi 06 mars.

Le dernier né de la Collection Framabook, édité chez InLibroVeritas, vient de sortir. « Changer pour OpenOffice.org », écrit, traduit et corrigé par un collectif d’auteurs, grâce à l’énergie de Johann, vous propose de migrer en douceur de Microsoft Office à OpenOffice.org.

Publié comme d’habitude sous une licence copyleft, ici la CC-by-sa, ce Framabook a donc bénéficié d’une implication importante de la communauté de OpenOffice et de Framasoft (traduction et correction) Livre issu d’un véritable travail collectif, nous espérons qu’il vous plaira et que vous aiderez à sa promotion. Livre en pré-commande, premières livraisons le 15 mars.

Extrait de la quatrième de couverture : Ce livre vous aidera en toute sérénité à passer de Microsoft Office à OpenOffice.org tout en conservant vos habitudes.

À l’instar de la suite bureautique Microsoft Office, OpenOffice.org propose un traitement de texte, un tableur, un gestionnaire de base de données, un module de présentation, un éditeur de dessin et un éditeur de formule mathématiques.

Déployée massivement dans l’Administration (Gendarmerie, Impôts, ministère de l’Equipement, ministère de la Culture…) et soutenue par des grands noms de l’informatique (Sun Microsystems, IBM…) cette suite bureautique a su s’imposer par sa simplicité d’utilisation et son efficacité.

Outre la gratuité, OpenOffice.org offre une solution pérenne pour la conservation des fichiers dans le temps grâce à l’utilisation du format OpenDocument, décrit par la norme internationale ISO 26300

  • Utilisez, créez et modifiez les fichiers de la suite Microsoft Office (.doc, .xls, .ppt, etc…).
  • Disponible sur les principales plates-formes Windows, GNU/Linux et MacOS.
  • Bénéficiez de mises à jour régulières et de l’aide d’une large majorité d’utilisateurs.
  • Créez des PDF de toutes tailles d’un seul clic.
  • « OpenOffice, vous l’apprenez une fois, vous l’appliquez partout »

A voir:

http://www.framabook.org/openoffice.html(« Il existe déjà une documentation riche et fournie autour de la suite bureautique OpenOffice.org, que ce soit sur le site du projet francophone ou sur Framasoft. Mais l’originalité de ce livre est de proposer une aide pour quitter Microsoft Office et adopter OpenOffice.org, en reprenant les différences entre ces deux suites bureautiques par modules (Word/OpenOffice Texte, Excel/OpenOffice Classeur, PowerPoint/ OpenOffice Présentation…)...Ce livre est une traduction libre du « Migration Guide » disponible sur http://oooauthors.org/en sous licence Creative Commons. Il a été traduit dans le cadre du projet Framalang, le groupe de traduction de Framasoft, sous l’impulsion de Johann Bulteau et en collaboration avec le projet francophone d’OpenOffice.org. »)

http://fr.wikipedia.org/wiki/OpenOffice.org (« OpenOffice.org (parfois abrégé en OOo ou OO.o) désigne à la fois une suite bureautique libre, une communauté de développeurs, et le site internet hébergeant l’ensemble du projet. Le but énoncé est «de créer, en tant que communauté, la suite bureautique internationale leader, tournant sur les principales plates-formes, et fournissant l’accès aux fonctionnalités et aux données via des composants et API ouverts et un format de données XML».

La suite bureautique est divisée en plusieurs modules pouvant interagir entre eux et partageant des concepts généraux communs:

Posted in Administration système, licence libre, logiciel libre, migration vers le libre, open source | Tagué: , | Leave a Comment »

Nouvelle version majeure de GCC : GCC 4.3.0

Posted by patrick sur mars 11, 2008

GCC est utilisé pour le développement de la plupart des logiciels libres. Le noyau Linux dépend notamment étroitement des fonctionnalités de GCC.

GCC 4.3.0 has been released. GCC 4.3.0 is a major release, containing substantial new functionality not available in GCC 4.2.x or previous GCC releases. See: http://gcc.gnu.org/gcc-4.3/changes.html for more information about changes in GCC 4.3.0.

There is one important caveat. It was discovered after the final release
has been made that some OS kernels on i?86 and x86_64 architectures
violate the processor specific ABI with regards to the DF flag, if a process
is interrupted with a signal while doing overlapping memmove or running some other code with DF flag set, the signal handler might be started with DF flag set on entry to the signal handler. GCC 4.3.0 no longer emits cld instructions unnecessarily, so GCC 4.3.0 compiled async signal handlers or functions the signal handlers call that rely on DF flag being cleared might misbehave. This will be hopefully fixed in the kernels soon and future GCC releases might provide an optional workaround for this bug.

Fixes for some systems:
Linux http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e40cd10ccff3d9fbffd57b93780bee4b7b9bff51
FreeBSD http://www.freebsd.org/cgi/query-pr.cgi?pr=121422
Hurd http://sources.redhat.com/ml/libc-alpha/2008-03/msg00020.html

http://gcc.gnu.org/gcc-4.3/changes.html (« GCC requires the GMP and MPFR libraries for building all the various front-end languages it supports. See the prerequisites page for version requirementsThe GCC middle-end has been integrated with the MPFR library. This allows GCC to evaluate and replace at compile-time calls to built-in math functions having constant arguments with their mathematically equivalent results. In making use of MPFR, GCC can generate correct results regardless of the math library implementation or floating point precision of the host platform. This also allows GCC to generate identical results regardless of whether one compiles in native or cross-compile configurations to a particular target….C++: Experimental support for the upcoming ISO C++ standard, C++0x. -Wc++0x-compat has been added and is now enabled by default for -Wall. It produces warnings for constructs whose meaning differs between ISO C++ 1998 and C++0x… An experimental parallel mode has been added. This is a parallel implementation of many C++ Standard library algorithms, like std::accumulate, std::for_each, std::transform, or std::sort, to give but four examples…Java: gcj now uses the Eclipse Java compiler for its Java parsing needs. This enables the use of all 1.5 language features, and fixes most existing front end bugs…Other significant improvements

  • The compiler’s --help command-line option has been extended so that it now takes an optional set of arguments. These arguments restrict the information displayed to specific classes of command-line options, and possibly only a subset of those options. It is also now possible to replace the descriptive text associated with each displayed option with an indication of its current value, or for binary options, whether it has been enabled or disabled.

    Here are some examples. The following will display all the options controlling warning messages:

          --help=warnings
        

    Whereas this will display all the undocumented, target specific options:

          --help=target,undocumented
        

    This sequence of commands will display the binary optimizations that are enabled by -O3:

          gcc -c -Q -O3 --help=optimizers > /tmp/O3-opts
          gcc -c -Q -O2 --help=optimizers > /tmp/O2-opts
          diff /tmp/O2-opts /tmp/O3-opts | grep enabled

« )

http://en.wikipedia.org/wiki/GNU_Compiler_Collection (« GCC was started by Richard Stallman in 1985. He extended an existing compiler to compile C. The compiler originally compiled Pastel, an extended, nonportable dialect of Pascal, and was written in Pastel. It was rewritten in C by Len Tower and Stallman,[4] and released in 1987[5] as the compiler for the GNU Project, in order to have a compiler available that was free software. Its development was supervised by the Free Software Foundation.« )

Posted in C++, Développement logiciel, GCC, java, programmation | Tagué: | Leave a Comment »

Des nouvelles de python: Sun supporte Jython et Python, Django, Mailman3 (MM3, REST), Barry Warsaw reçoit le prix Pizzigati pour GNU/Mailman

Posted by patrick sur mars 6, 2008

Jython et Sun

http://ironpython-urls.blogspot.com/2008/03/ironpython-has-serious-competition-sun.html (« In September 2006 Sun hired two JRuby developers to improve the story of dynamic languages on the JVM. This was seen by many as both long overdue and a response to Microsoft developing IronPython (and the Dynamic Language Runtime) for .NET. As Jython has been around for longer than JRuby, many in the Python community wondered why Sun weren’t supporting Python. Finally they have answered, by hiring Ted Leung and Jython lead developer Frank Wierzbicki.« )

http://www.sauria.com/blog/2008/03/03/the-sun-is-going-to-shine-on-python/ (…Over the years, I’ve met many people at Sun who understand a collaborative development style. Many of those folks are committers on Apache projects…How serious is Sun about dynamic languages and how deep does that support go? Sun is (finally?) very serious about this. As part of Sun’s new direction, Sun wants to give developers the ability to use whatever tool sets they want. Ruby, Python, PHP, Java. On or off OpenSolaris. On or off the JVM. There is an official project, John Rose’s DaVinci Machine Frank Wierzbicki, the maintainer of Jython, started at Sun last Monday, so there will be at least two of us working on Python related stuff. That includes Jython, Python support for Netbeans, and some other stuff that we haven’t quite figured out yet. We definitely will be looking for things that we can do to support CPython and the Python language as a whole. This is not just about Python on on the JVM. Sun will try to make its platforms, OpenSolaris and the JVM, the best place to develop and deploy Python applications. But at the moment that’s a goal and not a reality, so there is lots to do. )

http://fwierzbicki.blogspot.com/2008/02/jythons-future-looking-sunny.html (« …So by now you’ve probably guessed it: Sun Microsystems has hired me to work full time on Jython. They have also hired Ted Leung to represent the wider world of Python at Sun. I don’t think I can overstate just how excited I am about this. For a long time now I’ve been obsessed with Jython. Now I will be able to let my obsession take over completely…I have to especially thank Tim Bray, who has been pushing the dynamic language thing at Sun for quite a long time. I’m sure the warm welcome that I got at Sun was in no small part due to the enormous success of the JRuby work that has been going on there, so thanks to Charles Nutter and Thomas Enebo for their work. Also thanks to the many folks at Sun who have been pushing for this, including Eduardo Pelegri-Llopart. And of course thanks to all of you who use, contribute to, and talk about Jython. Jython is above all things a community effort. We should all share in the excitement. Hurray!« )

http://www.tbray.org/ongoing/When/200x/2008/03/03/Python-at-Sun (« So, as of this morning, noted Pythonista Ted Leung and Jython lead Frank Wierzbicki are joining Sun. Plus, we’re sponsoring PyCon and have applied to join the Python Software Foundation (it turns out you not only have to contribute, you have to get voted in). So, what are these guys going to be working on? I’m not sure. While we’re using Python internally for OpenSolaris IPS, nobody would call us real experts on the language. So my opinion is that Frank and Ted need build bridges to the community and figure out how we can help; if we can pitch in as well with Python as we have with Ruby, that’d be a win/win I’d say. Quick Python trivia question: Near as I can tell, Guido works half-time on Python over at Google. Is there anyone in the world, aside from Frank and Ted, getting paid to work full-time on Python ?« )

Django

  • http://www.jacobian.org/writing/2008/feb/21/sailing-on/ (« …However, I’ve been offered every Open Source developer’s dream job. Starting in March, I’ll be spending the majority of my time working on Django….So what exactly will I be doing? My job will entail a bit of internal-only closed-source development, but nearly everything I write will be Open Source. Most of my time will be spent improving Django. In the short term that’ll mean fixing tickets, working on new features, getting active branches finished and merged to trunk, and getting a one-point-omg release out the doorLast year I spent a few days in Boulder helping the Front Range Pythoneers kick off the Oracle backend for Django. It was a huge amount of fun, and I’m going to make myself available to other groups wanting to working on other similar problemsI can’t wait to spend my days hacking on Django. The best part is that this isn’t the only piece of good news about Django I’ll get to share this year. Stay tuned: 2008 is going to be huge« )

Mailman 3

  • http://wiki.list.org/display/DEV/REST+Interface (« I’m interested in working on a REST-style interface for controlling Mailman. One thought: should the web UI be written atop such a REST interface? Pro: it would nicely enforce decoupling the UI and the Mailman engine, and be a good test that the REST interface supports enough functionality. Con: adds an extra layer…I’m really keen on exploring this because I do think the decoupling will be a big win. It’ll let us distribute a turnkey, standalone u/i for those who want something working out of the box, but it’ll also let integrators use the core Mailman engine in their own sites. And it won’t limit you to just Python web frameworks (A sketch of the REST interface is in the wiki at http://wiki.list.org/display/DEV/REST+Interface . It’s written from the 2.1/2.2 point of view; I don’t know if mm3 reworks the basic objects so much that the REST interface no longer applies.). This interface isn’t intended to be exposed to the Internet at large, so there’s no mention of access control. It would be used as a back-end, on top of which the existing Mailman interface, or a fancy GUI application, or administrative scripts, could be built
    I think if we’re careful we can get pretty close. Ideally, we’d have
    the same REST api for both, which would give us a nice migration path, but I don’t yet know if that’s feasible. MM3 does have a more elaborate data model than MM2, but OTOH, everything is formally declared in Zope-style interfaces (and thoroughly tested… woohoo!). One thing that we have to figure out is how to represent all the metadata that currently lives in the Mailman.Gui package of 2.1/2.2. I think any web interface acting through the REST api will want that basic information, e.g. the brief and detailed descriptions of the mailing attributes (the VARHELP). I’m sure there’s a clear way to publish that through the REST api, but it might have an impact on the format used. I like JSON a lot, but html or xml might be more amenable to that type of data. OTOH, it’s all read-only so it might make sense to split it into two trees of information.
    « )

Mailman

  • http://mail.python.org/mailman/listinfo/mailman-announce(« 
    I realize that I’ve been remiss in announcing this. My apologies. I have been awarded the 2008 Pizzigati Prize for Public Interest
    Computing for GNU Mailman. http://www.pizzigatiprize.org/
    I am deeply honored to win this prize because I believe very strongly
    in Mailman’s role in helping people communicate and organize. I want
    to thank all of you who have supported me and Mailman over the years, and I want to let you know that I am as excited as ever about where Mailman is going. One of the most satisfying aspects of this project for me has been meeting you, the users, developers and contributors to Mailman, both online and face-to-face. I’m looking forward to meeting the Pizzigati family and having some time to spend with them learning about Anthony’s remarkable life, sadly cut too short. So again, thank you all and I’m looking forward to the next 10 years of GNU Mailman!Cheers,
    – -Barry »)
  • http://www.pizzigatiprize.org/news/press_releases/barry_warsaw_named_second_annual_winner_of_the_10,000_pizzigati_prize.html (« San Francisco, January 30, 2008— Tides Foundation announces the winner of the second annual $10,000 Pizzigati Prize. Barry Warsaw, a software developer dedicated to identifying and solving the technological problems that confront social change movements, has won the Antonio Pizzigati Prize for Software in the Public Interest.
    Barry Warsaw is being recognized for his work as the lead developer of GNU Mailman, the open source application that hundreds of nonprofits around the world are now using to manage electronic mail discussions and e-newsletter lists. The Pizzigati Prize — an award program launched two years ago by Tides Foundation’s Florence and Frances Family Fund — aims to honor individuals who, in the spirit of open source computing, fashion outstanding applications that help nonprofits become more effective in their ongoing social change efforts. “Barry Warsaw has displayed, over the years, a powerful personal commitment to the ideals behind the Pizzigati Prize,” notes Jason Sanders, Tides Philanthropic Advisor who coordinates the prize competition. “His work has demonstrated vision and inspired innovation in public interest computing
    .« )

Posted in jython, logiciel libre, python, REST, Web Frameworks | Tagué: , , , | 2 Comments »

Nouvelles versions de python: Python 2.6a1 et 3.0a3

Posted by patrick sur mars 3, 2008

Source: http://mail.python.org/mailman/listinfo/python-3000

On behalf of the Python development team and the Python community, I’m happy to announce the first alpha release of Python 2.6, and the third alpha release of Python 3.0.

Python 2.6 is not only the next advancement in the Python 2 series, it is also a transitionary release, helping developers begin to prepare their code for Python 3.0. As such, many features are being backported from Python 3.0 to 2.6. It makes sense to release both versions in at the same time, the precedence for this having been set with the Python 1.6 and 2.0 releases.

During the alpha testing cycle we will be releasing both versions in lockstep, on a monthly release cycle. The releases will happen on the last Friday of every month. If this schedule works well, we will continue releasing in lockstep during the beta program. See PEP 361
for schedule details:

http://www.python.org/dev/peps/pep-0361/

Please note that these are alpha releases, and as such are not suitable for production environments. We continue to strive for a high degree of quality, but there are still some known problems and the feature sets have not been finalized. These alphas are being released to solicit feedback and hopefully discover bugs, as well as allowing you to determine how changes in 2.6 and 3.0 might impact you. If you find things broken or incorrect, please submit a bug report at http://bugs.python.org

For more information and downloadable distributions, see the Python
2.6 web site:

http://www.python.org/download/releases/2.6/

and the Python 3.0 web site:

http://www.python.org/download/releases/3.0/

We are planning a number of additional alpha releases, with the final release schedule still to be determined.

Enjoy,
– -Barry

Barry Warsaw
barry@python.org
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

Posted in 2008, python | Tagué: , | Leave a Comment »

C++ et la métaprogrammation avec les templates, le nouveau standard C++0x pour C++

Posted by patrick sur mars 3, 2008

Source: un article publié dans le magazine Programmez! de Frédéric Mazué sur “Blitz++ et la méta-programmation C++ ».

« …quand C++ s’est vu doté des templates, des programmeurs astucieux les ont détournés de leur usage premier. La méta-programmation C++ était née, et un gain significatif de performance avec elle…ce n’est pas une bonne idée que de vouloir faire de la méta-programmation à tout prix. Par contre c’est une bonne idée d’utiliser des librairies telles que Boost et Blitz++ dont la méta-programmtion est une pierre angulaire« .

A voir:

  • http://fr.wikipedia.org/wiki/M%C3%A9taprogrammation (« La métaprogrammation avec des patrons est une technique de programmation dans laquelle les patrons sont utilisés de sorte que le compilateur, lors de la compilation du code, exécute un programme. Ces programmes peuvent générer des constantes ou des structures de données. Cette technique est utilisée principalement dans le langage de programmation C++…La métaprogrammation avec des patrons a des utilisations pratiques malgré son apparence maladroite. Elle peut être utilisée pour créer des classes vecteur à n dimensions quand n est connu à la compilation. L’avantage par rapport à un vecteur à n dimensions traditionnel est que les boucles peuvent être déroulées, ce qui produit un code très optimisé. »)
  • http://en.wikipedia.org/wiki/C%2B%2B0x (« C++0x is the planned new standard for the C++ programming language. It is intended to replace the existing C++ standard, ISO/IEC 14882, which was published in 1998 and updated in 2003. These predecessors are informally known as C++98 and C++03. The new standard will include several additions to the core language and will extend the C++ standard library, incorporating most of the C++ Technical Report 1 libraries — most likely with the exception of the library of mathematical special functions. Since the standard is not yet finalized, this article may not reflect the most recent state of C++0x. Up-to-date state of the next C++ standard is published on the ISO C++ committee website. The most recent report, N2432, was published in October 2007. »)
  • http://www.oonumerics.org/blitz/ (« Blitz++ is a C++ class library for scientific computing which provides performance on par with Fortran 77/90. It uses template techniques to achieve high performance. The current versions provide dense arrays and vectors, random number generators, and small vectors and matrices. Blitz++ is distributed freely under an open source license, and contributions to the library are welcomed. « )
  • http://www.boost.org/ (« Boost provides free peer-reviewed portable C++ source libraries. We emphasize libraries that work well with the C++ Standard Library. Boost libraries are intended to be widely useful, and usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use.C++ Standards Committee’s Library Technical Report ( TR1) as a step toward becoming part of a future C++ Standard. More Boost libraries are proposed for the upcoming TR2 We aim to establish « existing practice » and provide reference implementations so that Boost libraries are suitable for eventual standardization. Ten Boost libraries are already included in the . »)
  • http://en.wikipedia.org/wiki/Boost_C%2B%2B_Libraries (« …The libraries are aimed at a wide range of C++ users and application domains. They range from general-purpose libraries like SmartPtr, to OS Abstractions like FileSystem, to libraries primarily aimed at other library developers and advanced C++ users, like MPL. In order to ensure efficiency and flexibility, Boost makes extensive use of templates. Boost has been a source of extensive work and research into generic programming and metaprogramming in C++…« )
  • http://en.wikipedia.org/wiki/GNU_Compiler_Collection (« …The GNU Compiler Collection (usually shortened to GCC) is a set of compilers produced for various programming languages by the GNU Project. GCC is a key component of the GNU toolchain. As well as being the official compiler of the GNU system, GCC has been adopted as the standard compiler by most other modern Unix-like computer operating systems, including Linux, the BSD family and Mac OS X. GCC has been ported to a wide variety of computer architectures, and is widely deployed as a tool in commercial, proprietary and closed source software development environments. GCC is also used in popular embedded platforms like Symbian[1], Playstation and Sega Dreamcast. Originally named the GNU C Compiler, because it only handled the C programming language, GCC 1.0 was released in 1987, and the compiler was extended to compile C++ in December of that year.[2] Front ends were later developed for Fortran, Pascal, Objective C, Java, and Ada, among others...GCC 4.2.1 will be the last release of GCC covered by version 2 of the GNU General Public License. All future releases will be released under GPL version 3. » « )

Posted in C++, métaprogrammation | Tagué: | 1 Comment »