On 9/24/18 6:37 PM, Rodion Iafarov wrote:
1) Will YCP be dropped in foreseeable future, if yes what shall be used instead? yaml+ruby?
I might add that this is also about the low-level YCP container classes such
as YCPValue, YCPList, YCPMap, YCPString etc. - and, most importantly, YCPTerm
which is what the UI interpreter uses heavily. It doesn't really use any
"real" YCP stuff, but it revolves around those YCPValue-related container
classes.
Should we decide to drop that completely, we will have to come up with an
alternative which in all likelyhood will work in a very similar way; the UI
interpreter needs some container classes for transporting the UI terms from
the application layer (no matter if it's YCP, Ruby, Perl or Python) to the UI
C++ classes.
The alternative would be to rewrite all UI-related application code
completely, using "new" for new objects and passing their parent as a parameter.
With the amount of UI terms we have all over the YaST code I don't think this
is realistic for the forseeable future. We'd break 99.9% of all YaST code.
Having said that, I don't believe those YCPValue-related classes will go away
in the forseeable future.
The macro player which basically uses YCP "eval" to execute a chunk of code
for each macro segment is another matter. We'll have to think about that.
(I had talked with Rodion about most of this; this is just a recap for those
who were not part of that discussion.)
Kind regards
--
Stefan Hundhammer