Programming Language, AFAIK

On Mon, Mar 24, 2014 at 11:46 AM, Oleg Gelbukh <ogelb...@mirantis.com>wrote:

> What does PL stand for, anyway?
>
> --
> Best regards,
> Oleg Gelbukh
>
>
> On Mon, Mar 24, 2014 at 11:39 AM, Serg Melikyan <smelik...@mirantis.com>wrote:
>
>> >because 'dsl'/'language' terms are too broad.
>> Too broad in general, but we choose name for sub-package, and in murano
>> term 'language' mean Murano PL.
>>
>> +1 for language
>>
>>
>> On Mon, Mar 24, 2014 at 11:26 AM, Timur Sufiev <tsuf...@mirantis.com>wrote:
>>
>>> +1 for muranoapi.engine.murano_pl, because 'dsl'/'language' terms are
>>> too broad.
>>>
>>> On Mon, Mar 24, 2014 at 12:48 AM, Timur Nurlygayanov
>>> <tnurlygaya...@mirantis.com> wrote:
>>> > Hi Serg,
>>> >
>>> > This idea sounds good, I suggest to use name 'murano.engine.murano_pl'
>>> (not
>>> > just common name like 'language' or 'dsl', but name, which will be
>>> based on
>>> > 'MuranoPL')
>>> >
>>> > Do we plan to support the ability to define different languages for
>>> Murano
>>> > Engine?
>>> >
>>> >
>>> > Thank you!
>>> >
>>> >
>>> > On Sun, Mar 23, 2014 at 1:05 PM, Serg Melikyan <smelik...@mirantis.com
>>> >
>>> > wrote:
>>> >>
>>> >> There is a idea to separate core of Murano PL implementation from
>>> engine
>>> >> specific code, like it was done in PoC. When this two things are
>>> separated
>>> >> in different packages, we will be able to track and maintain our
>>> language
>>> >> core as clean as possible from engine specific code. This will give
>>> to us an
>>> >> ability to easily separate our language implementation to a library.
>>> >>
>>> >> Questions is under what name we should place core of Murano PL?
>>> >>
>>> >> 1) muranoapi.engine.language;
>>> >> 2) muranoapi.engine.dsl;
>>> >> 3) suggestions?
>>> >>
>>> >> --
>>> >> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>>> >> http://mirantis.com | smelik...@mirantis.com
>>> >>
>>> >> +7 (495) 640-4904, 0261
>>> >> +7 (903) 156-0836
>>> >>
>>> >> _______________________________________________
>>> >> OpenStack-dev mailing list
>>> >> OpenStack-dev@lists.openstack.org
>>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> >
>>> > Timur,
>>> > QA Engineer
>>> > OpenStack Projects
>>> > Mirantis Inc
>>> >
>>> > _______________________________________________
>>> > OpenStack-dev mailing list
>>> > OpenStack-dev@lists.openstack.org
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >
>>>
>>>
>>>
>>> --
>>> Timur Sufiev
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>>
>> --
>> Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
>> http://mirantis.com | smelik...@mirantis.com
>>
>> +7 (495) 640-4904, 0261
>> +7 (903) 156-0836
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelik...@mirantis.com

+7 (495) 640-4904, 0261
+7 (903) 156-0836
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to