On Tue, Dec 6, 2016 at 12:47 PM, 'Terry Brown' via leo-editor <[email protected]> wrote: > (How I feel about clones, YMMV) > ... > I can see why people are attracted to clones for this second category of > .... In code, wanting to > repeat things may indicate bad design, you can usually define something > somewhere and reference it by name in the manner appropriate to the language > you're using.... >
IMHO, only issue case in coding ;-) '''... repeat things may indicate bad design''' ~ can not agree more but, this feeling just only base the release stage of project, in software more than 80% stage is in chaos, every things be try/testing/adjusting/etc. so Leo can very happy ctrl. all kinds of chaos code block, with section/@others/clone/etc. the software big picture, always under us design. for me in coding , clone usage: - in-sync same config/information in difference file/dir/proj. - in-sync function code block, but not yet extract as function/class/module - in-sync temporary demo data, not necessary as data file - ... for fix `repeat things`, every cloned node just the target will replace with one function, but not in beginning, just with project developing, natural/slowly/one by one replaced. PS: lamentable...most project will die, before all cloned nodes replace with good look function.... > Cheers -Terry > > -- life is pathetic, go Pythonic! 人生苦短, Python当歌! 俺: http://zoomquiet.io 授: http://creativecommons.org/licenses/by-sa/2.5/cn/ 怒: 冗余不做,日子甭过!备份不做,十恶不赦! KM keep growing environment culture which promoting organization be learnning! -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
