Eiffel: What's the difference between an “eiffel” library and a gobo library?












0















Eiffel: What's the difference between an "eiffel" library and a gobo library? for example with xml, which should I choose and why?



enter image description here










share|improve this question



























    0















    Eiffel: What's the difference between an "eiffel" library and a gobo library? for example with xml, which should I choose and why?



    enter image description here










    share|improve this question

























      0












      0








      0








      Eiffel: What's the difference between an "eiffel" library and a gobo library? for example with xml, which should I choose and why?



      enter image description here










      share|improve this question














      Eiffel: What's the difference between an "eiffel" library and a gobo library? for example with xml, which should I choose and why?



      enter image description here







      eiffel






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 15 '18 at 10:57









      PipoPipo

      1,6281627




      1,6281627
























          1 Answer
          1






          active

          oldest

          votes


















          2














          Initially EiffelSoftware XML library was built an alternative/replacement for Gobo XML, because Gobo was not Void-safe at that time.
          Also, Eiffel XML does not depend on the Gobo package (many good Eiffel libraries, that uses their own structures, own files interfaces and so on).
          Eiffel XML is based on EiffelBase, and does not bring all the Gobo dependencies.



          Note also, Gobo XML callbacks are using STRING, and variants of UC_STRING, while Eiffel XML uses directly STRING_32.
          Eiffel XML supports only ASCII, and UTF-8 encoding, while Gobo XML has stronger encoding support via the descendants of UC_STRING.
          Gobo XML is may be more complete (but this needs to be checked).



          So the choice really depends on your needs.
          If your application is already using Gobo structures, then you should probably use Gobo XML.
          Otherwise I would suggest to use Eiffel XML (unless Eiffel XML does not support the encoding you care about).






          share|improve this answer
























          • Thx!, could you provide a brief description of what is gobo and EiffelSoftware library

            – Pipo
            Nov 15 '18 at 14:47











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317898%2feiffel-whats-the-difference-between-an-eiffel-library-and-a-gobo-library%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          2














          Initially EiffelSoftware XML library was built an alternative/replacement for Gobo XML, because Gobo was not Void-safe at that time.
          Also, Eiffel XML does not depend on the Gobo package (many good Eiffel libraries, that uses their own structures, own files interfaces and so on).
          Eiffel XML is based on EiffelBase, and does not bring all the Gobo dependencies.



          Note also, Gobo XML callbacks are using STRING, and variants of UC_STRING, while Eiffel XML uses directly STRING_32.
          Eiffel XML supports only ASCII, and UTF-8 encoding, while Gobo XML has stronger encoding support via the descendants of UC_STRING.
          Gobo XML is may be more complete (but this needs to be checked).



          So the choice really depends on your needs.
          If your application is already using Gobo structures, then you should probably use Gobo XML.
          Otherwise I would suggest to use Eiffel XML (unless Eiffel XML does not support the encoding you care about).






          share|improve this answer
























          • Thx!, could you provide a brief description of what is gobo and EiffelSoftware library

            – Pipo
            Nov 15 '18 at 14:47
















          2














          Initially EiffelSoftware XML library was built an alternative/replacement for Gobo XML, because Gobo was not Void-safe at that time.
          Also, Eiffel XML does not depend on the Gobo package (many good Eiffel libraries, that uses their own structures, own files interfaces and so on).
          Eiffel XML is based on EiffelBase, and does not bring all the Gobo dependencies.



          Note also, Gobo XML callbacks are using STRING, and variants of UC_STRING, while Eiffel XML uses directly STRING_32.
          Eiffel XML supports only ASCII, and UTF-8 encoding, while Gobo XML has stronger encoding support via the descendants of UC_STRING.
          Gobo XML is may be more complete (but this needs to be checked).



          So the choice really depends on your needs.
          If your application is already using Gobo structures, then you should probably use Gobo XML.
          Otherwise I would suggest to use Eiffel XML (unless Eiffel XML does not support the encoding you care about).






          share|improve this answer
























          • Thx!, could you provide a brief description of what is gobo and EiffelSoftware library

            – Pipo
            Nov 15 '18 at 14:47














          2












          2








          2







          Initially EiffelSoftware XML library was built an alternative/replacement for Gobo XML, because Gobo was not Void-safe at that time.
          Also, Eiffel XML does not depend on the Gobo package (many good Eiffel libraries, that uses their own structures, own files interfaces and so on).
          Eiffel XML is based on EiffelBase, and does not bring all the Gobo dependencies.



          Note also, Gobo XML callbacks are using STRING, and variants of UC_STRING, while Eiffel XML uses directly STRING_32.
          Eiffel XML supports only ASCII, and UTF-8 encoding, while Gobo XML has stronger encoding support via the descendants of UC_STRING.
          Gobo XML is may be more complete (but this needs to be checked).



          So the choice really depends on your needs.
          If your application is already using Gobo structures, then you should probably use Gobo XML.
          Otherwise I would suggest to use Eiffel XML (unless Eiffel XML does not support the encoding you care about).






          share|improve this answer













          Initially EiffelSoftware XML library was built an alternative/replacement for Gobo XML, because Gobo was not Void-safe at that time.
          Also, Eiffel XML does not depend on the Gobo package (many good Eiffel libraries, that uses their own structures, own files interfaces and so on).
          Eiffel XML is based on EiffelBase, and does not bring all the Gobo dependencies.



          Note also, Gobo XML callbacks are using STRING, and variants of UC_STRING, while Eiffel XML uses directly STRING_32.
          Eiffel XML supports only ASCII, and UTF-8 encoding, while Gobo XML has stronger encoding support via the descendants of UC_STRING.
          Gobo XML is may be more complete (but this needs to be checked).



          So the choice really depends on your needs.
          If your application is already using Gobo structures, then you should probably use Gobo XML.
          Otherwise I would suggest to use Eiffel XML (unless Eiffel XML does not support the encoding you care about).







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 15 '18 at 13:08









          JocelynJocelyn

          49348




          49348













          • Thx!, could you provide a brief description of what is gobo and EiffelSoftware library

            – Pipo
            Nov 15 '18 at 14:47



















          • Thx!, could you provide a brief description of what is gobo and EiffelSoftware library

            – Pipo
            Nov 15 '18 at 14:47

















          Thx!, could you provide a brief description of what is gobo and EiffelSoftware library

          – Pipo
          Nov 15 '18 at 14:47





          Thx!, could you provide a brief description of what is gobo and EiffelSoftware library

          – Pipo
          Nov 15 '18 at 14:47




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317898%2feiffel-whats-the-difference-between-an-eiffel-library-and-a-gobo-library%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Xamarin.iOS Cant Deploy on Iphone

          Glorious Revolution

          Dulmage-Mendelsohn matrix decomposition in Python