"templatizable" meaning in English

{
  "etymology_templates": [
    {
      "args": {
        "1": "en",
        "2": "templatize",
        "3": "able"
      },
      "expansion": "templatize + -able",
      "name": "suffix"
    }
  ],
  "etymology_text": "From templatize + -able.",
  "head_templates": [
    {
      "args": {
        "1": "-"
      },
      "expansion": "templatizable (not comparable)",
      "name": "en-adj"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "adj",
  "senses": [
    {
      "categories": [
        {
          "kind": "other",
          "name": "English entries with incorrect language header",
          "parents": [
            "Entries with incorrect language header",
            "Entry maintenance"
          ],
          "source": "w"
        },
        {
          "kind": "other",
          "name": "English terms suffixed with -able",
          "parents": [],
          "source": "w"
        },
        {
          "kind": "other",
          "name": "Entries with translation boxes",
          "parents": [],
          "source": "w"
        },
        {
          "kind": "other",
          "name": "Pages with 1 entry",
          "parents": [],
          "source": "w"
        },
        {
          "kind": "other",
          "name": "Pages with entries",
          "parents": [],
          "source": "w"
        },
        {
          "kind": "topical",
          "langcode": "en",
          "name": "Computing",
          "orig": "en:Computing",
          "parents": [
            "Technology",
            "All topics",
            "Fundamental"
          ],
          "source": "w"
        }
      ],
      "examples": [
        {
          "ref": "1998 September 21, John Potter, \"Re: operator+(C c1, const C& c2)\", in comp.lang.c++.moderated, Usenet",
          "text": "They are equally templatizable and inlinable."
        },
        {
          "ref": "2006 August 22, The Ghost In The Machine, “Re: Java FACT ?”, in comp.lang.java.advocacy (Usenet):",
          "text": "Closures would be reassignable and templatizable, and of course used as values, leading to some ugly syntax without typedefs, but one could contemplate something along the following lines: […]",
          "type": "quote"
        },
        {
          "ref": "2006 December 17, \"The Ghost In The Machine\" (username), \"Re: Goto's labels makes code _Tons_ more readable ( and lest nested ).\", in sci.physics and alt.usenet.kooks, Usenet",
          "text": "One can also split the problem into pieces, which gets kind of ugly in C, but might be templatizable in C++: […]"
        },
        {
          "ref": "2007 January 22, \"noone\" (username), \"work related dig regarding separation of definitions and implementations\", in comp.lang.c++, Usenet",
          "text": "Next, TTBOMK you need to do your classes in header files if you are going to make them into generic templates...well, putting them into headers isn't strictly a requirement but the other restrictions for (templatizable code) would encourage only using headers."
        }
      ],
      "glosses": [
        "Able to be templatized."
      ],
      "id": "en-templatizable-en-adj-EfEJt9V8",
      "links": [
        [
          "computing",
          "computing#Noun"
        ],
        [
          "templatize",
          "templatize"
        ]
      ],
      "raw_glosses": [
        "(computing, rare) Able to be templatized."
      ],
      "tags": [
        "not-comparable",
        "rare"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "sciences"
      ]
    }
  ],
  "word": "templatizable"
}

{
  "etymology_templates": [
    {
      "args": {
        "1": "en",
        "2": "templatize",
        "3": "able"
      },
      "expansion": "templatize + -able",
      "name": "suffix"
    }
  ],
  "etymology_text": "From templatize + -able.",
  "head_templates": [
    {
      "args": {
        "1": "-"
      },
      "expansion": "templatizable (not comparable)",
      "name": "en-adj"
    }
  ],
  "lang": "English",
  "lang_code": "en",
  "pos": "adj",
  "senses": [
    {
      "categories": [
        "English adjectives",
        "English entries with incorrect language header",
        "English lemmas",
        "English terms suffixed with -able",
        "English terms with quotations",
        "English terms with rare senses",
        "English uncomparable adjectives",
        "Entries with translation boxes",
        "Pages with 1 entry",
        "Pages with entries",
        "en:Computing"
      ],
      "examples": [
        {
          "ref": "1998 September 21, John Potter, \"Re: operator+(C c1, const C& c2)\", in comp.lang.c++.moderated, Usenet",
          "text": "They are equally templatizable and inlinable."
        },
        {
          "ref": "2006 August 22, The Ghost In The Machine, “Re: Java FACT ?”, in comp.lang.java.advocacy (Usenet):",
          "text": "Closures would be reassignable and templatizable, and of course used as values, leading to some ugly syntax without typedefs, but one could contemplate something along the following lines: […]",
          "type": "quote"
        },
        {
          "ref": "2006 December 17, \"The Ghost In The Machine\" (username), \"Re: Goto's labels makes code _Tons_ more readable ( and lest nested ).\", in sci.physics and alt.usenet.kooks, Usenet",
          "text": "One can also split the problem into pieces, which gets kind of ugly in C, but might be templatizable in C++: […]"
        },
        {
          "ref": "2007 January 22, \"noone\" (username), \"work related dig regarding separation of definitions and implementations\", in comp.lang.c++, Usenet",
          "text": "Next, TTBOMK you need to do your classes in header files if you are going to make them into generic templates...well, putting them into headers isn't strictly a requirement but the other restrictions for (templatizable code) would encourage only using headers."
        }
      ],
      "glosses": [
        "Able to be templatized."
      ],
      "links": [
        [
          "computing",
          "computing#Noun"
        ],
        [
          "templatize",
          "templatize"
        ]
      ],
      "raw_glosses": [
        "(computing, rare) Able to be templatized."
      ],
      "tags": [
        "not-comparable",
        "rare"
      ],
      "topics": [
        "computing",
        "engineering",
        "mathematics",
        "natural-sciences",
        "physical-sciences",
        "sciences"
      ]
    }
  ],
  "word": "templatizable"
}