|Subject:||Re: [Liberty-eiffel] PATH_NAME. make from string|
|Date:||Fri, 25 Jul 2014 21:51:38 +0200|
Being very memory conservative is a paramount design requirement in standard libraries.
Thinking better about it it may be wiser to use ABSTRACT_STRING.string feature in user code. I would remove the "put for elks compatibility" note: is the old elks relevant anymore? I don't think so. "reasonable, best effort" compatibility with ISE is somehow preferable, for a feasible and comfortable definition on the terms :-)
>Cyril, in holidays too, but working on backup automation procedures at>home (hence the late hour) :-)That's reminds me that I shall ditch GlusterFS in favor of Ceph AND deploy a "real" backup. What's your approach? Offline, online, remote, on the cloud ?
|[Prev in Thread]||Current Thread||[Next in Thread]|