On Thu, Jun 19, 2014 at 11:17 AM, Tom Hacohen <tom.haco...@samsung.com> wrote: > On 19/06/14 15:01, Carsten Haitzler (The Rasterman) wrote:
[snip] > Though I wonder if there's a way to put that outside of the .eo, and > into .eo.doc overrides per language that add more info and are contained > elsewhere. Reason for that being, is that it's really not .eo related. Actually it is, I even thought about separating per language on its own file (.eo.c.doc), but that would replicate the function signatures. But I think documentation, be that specific or not is eo-based because it says what the function does and how to use it. Semantics is a part of the interface as much as signatures. So I think the same eo file is best to reduce redundancy and avoid out-of-sync errors too. > -- > Tom. -- Felipe Magno de Almeida ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
