Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
packagestructure [2016/02/29 11:50]
christian [PDF]
packagestructure [2016/09/24 08:16] (current)
dokuadmin ↷ Page moved from pdf:packagestructure to packagestructure
Line 90: Line 90:
 The Values package is my base library for almost everything I do. It provides Values (as opposed to Objects) which are simple, immutable objects. Values can only be created but never modified. This allows for a functional programming style and simplyfies systems, since much less state has to be maintained. Especially I like to see all structure and details (of complex values) at a glance and the ease of creating test values. The Values package is my base library for almost everything I do. It provides Values (as opposed to Objects) which are simple, immutable objects. Values can only be created but never modified. This allows for a functional programming style and simplyfies systems, since much less state has to be maintained. Especially I like to see all structure and details (of complex values) at a glance and the ease of creating test values.
  
-I wrote a (scientific) dry paper about it and presented it at ESUG 2009 in Brest. I think that nobody understood it... :-). One can buy the [[http://dl.acm.org/citation.cfm?id=1735935&jmp=cit&coll=GUIDE&dl=GUIDE#CIT|paper from the ACM]]. The slides of the talk are [[http://vst.ensm-douai.fr/ESUG2009Media/uploads/1/complex_values_haider.pdf|here]]. On request, I could send you draft of the paper on which the ACM does not have the copyright :-).+I wrote a (scientific) dry paper about it and presented it at ESUG 2009 in Brest. I think that nobody understood it... :-). One can buy the [[http://dl.acm.org/citation.cfm?id=1735935&jmp=cit&coll=GUIDE&dl=GUIDE#CIT|paper from the ACM]]. The slides of the talk are [[http://vst.ensm-douai.fr/ESUG2009Media/uploads/1/complex_values_haider.pdf|here]]. Or you can see the {{:values:complexvaluespaper.pdf|draft}} of the paper with identical content on which the ACM does not have the copyright
  
 For porting, I would strongly suggest to start with (parts of) the Values code. But this should not be too much of a problem, since you do not need everything. The "Values" package contains all essential runtime code: Value class, the value printer and compatibility methods for system classes to be used as values. That is sufficient to implement the existing Value subclasses used by Fonts and PDF. The "Values Development" package adds the ability to generate methods for your own Value subclasses. This would not be strictly necessary for porting PDF or Fonts. For porting, I would strongly suggest to start with (parts of) the Values code. But this should not be too much of a problem, since you do not need everything. The "Values" package contains all essential runtime code: Value class, the value printer and compatibility methods for system classes to be used as values. That is sufficient to implement the existing Value subclasses used by Fonts and PDF. The "Values Development" package adds the ability to generate methods for your own Value subclasses. This would not be strictly necessary for porting PDF or Fonts.
  • packagestructure.1456743011.txt.gz
  • Last modified: 2016/02/29 11:50
  • by christian