{"id":12112,"date":"2022-09-29T16:52:50","date_gmt":"2022-09-29T11:22:50","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/"},"modified":"2022-09-29T16:52:50","modified_gmt":"2022-09-29T11:22:50","slug":"solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/","title":{"rendered":"[Solved] Error\t2\terror C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int"},"content":{"rendered":"<p> [ad_1]<br \/>\n<\/p>\n<div id=\"answer-20620283\" class=\"answer js-answer accepted-answer js-accepted-answer\" data-answerid=\"20620283\" data-parentid=\"20580387\" data-score=\"4\" data-position-on-page=\"1\" data-highest-scored=\"1\" data-question-has-accepted-highest-score=\"1\" itemprop=\"acceptedAnswer\" itemscope itemtype=\"https:\/\/schema.org\/Answer\">\n<div class=\"post-layout\">\n<div class=\"votecell post-layout--left\"><\/div>\n<div class=\"answercell post-layout--right\">\n<div class=\"s-prose js-post-body\" itemprop=\"text\">\n<p>This is actually a rather interesting error; the error message doesn&#8217;t do much to tell you what the problem is.<\/p>\n<p>My initial speculation was largely incorrect, but I&#8217;ve left it in place for now. See below.<\/p>\n<p>This code:<\/p>\n<pre><code>#ifndef uint32_t\n#define unsigned int    uint32_t;\n#endif\n<\/code><\/pre>\n<p>is incorrect.  The name of the macro being defined goes immediately after the <code>#define<\/code>, and a macro definition normally should not include a semicolon. (Macro definition syntax is quite different from declaration syntax.) Rather than defining <code>uint32_t<\/code>, this defines <code>unsigned<\/code>, and attempting to redefine a language keyword can cause serious problems. Also, the <code>#ifndef<\/code> is not useful, since the <code>uint32_t<\/code>, if it&#8217;s defined via <code>\"stdafx.h\"<\/code>, is a typedef, not a macro. You can use <code>#ifdef UINT32_MAX<\/code> to check whether `uint32_t has been defined.  A correct version is:<\/p>\n<pre><code>#ifndef UINT32_MAX\n#define uint32_t unsigned int\n#endif\n<\/code><\/pre>\n<p>or, even better:<\/p>\n<pre><code>#ifndef UINT32_MAX\ntypedef unsigned int uint32_t;\n#endif\n<\/code><\/pre>\n<p>That needs to be fixed, but it didn&#8217;t cause the problem you&#8217;re seeing.  Apparently <code>uint32_t<\/code> is not defined in your implementation, causing this declaration:<\/p>\n<pre><code>uint32_t    emp_id;\n<\/code><\/pre>\n<p>to fail.<\/p>\n<p>The error message is still misleading. Since <code>uint32_t<\/code> has not been declared, it&#8217;s treated as an ordinary identifier, not as a type name &#8212; and type names are treated as <em>syntactically<\/em> distinct from ordinary identifiers. The compiler attempted to recover from the error by guessing that <code>uint32_t<\/code> might be a member name, which means it should be followed by a semicolon &#8212; but then the declaration<\/p>\n<pre><code>uint32_t;\n<\/code><\/pre>\n<p>would declare a member with no explicit type. In old versions of C, this would be legal and would make the member an <code>int<\/code>. The compiler&#8217;s guess about what the code actually meant was wrong.<\/p>\n<p>Incidentally, if you show an error message, <em>please<\/em> tell us which line it applies to.<\/p>\n<hr>\n<p>My initial speculation about the cause of the problem, which turned out to be incorrect follows. I had guessed that _TCHAR was a macro, but it&#8217;s actually a <code>typedef<\/code>.<\/p>\n<hr>\n<p>The macro definition:<\/p>\n<pre><code>#ifndef uint32_t\n#define unsigned int    uint32_t;\n#endif\n<\/code><\/pre>\n<p>has several levels of wrongness.  In a macro definition, the macro being defined goes first, followed by the sequence that it expands to &#8212; which usually should <em>not<\/em> be terminated by a semicolon:<\/p>\n<pre><code>#define uint32_t unsigned int\n<\/code><\/pre>\n<p>But using a macro for this purpose is a bad idea; a <code>typedef<\/code> is much better:<\/p>\n<pre><code>typedef unsigned int uint32_t;\n<\/code><\/pre>\n<p>(note that the identifier being defined goes last, and a semicolon is required; macro definitions and <code>typedef<\/code>s have very different syntax).  And unlike macros, there&#8217;s no way to test whether a <code>typedef<\/code> has already been defined.<\/p>\n<p>The <code>uint32_t<\/code> should already be defined in <code>&lt;stdint.h&gt;<\/code> or <code>&lt;cstdint&gt;<\/code> &#8212; but that&#8217;s a standard header that was added to C by the 1999 ISO C standard, and adopted in C++ only by the 2011 ISO C++ standard, so there&#8217;s a decent chance that it won&#8217;t be available, depending on what C++ implementation you&#8217;re using.  If the header exists, you can use <code>#ifdef UINT_MAX<\/code> to determine whether <code>uint32_t<\/code> is defined, but that&#8217;s only useful if you&#8217;re concerned about systems that don&#8217;t have a 32-bit unsigned type at all.<\/p>\n<p>But your code doesn&#8217;t even refer to <code>uint32_t<\/code> &#8212; so why did the macro definition cause a problem?<\/p>\n<p>Because you got the order wrong, your macro definition doesn&#8217;t define <code>uint32_t<\/code>, it defines <code>unsigned<\/code>, so that any occurrence of that word will expand to <code>int uint32_t;<\/code> (including the semicolon).<\/p>\n<p>But you don&#8217;t refer to <code>unsigned<\/code> either &#8212; at least not directly.  The problem, then, is in your definition of <code>_tmain<\/code>:<\/p>\n<pre><code>int _tmain(int argc, _TCHAR* argv[])\n<\/code><\/pre>\n<p>Both <code>_tmain<\/code> as the program entry point and the type name <code>_TCHAR<\/code> are Microsoft-specific. I don&#8217;t have access to a Microsoft compiler at the moment, but judging by the error message you&#8217;re seeing, <code>_TCHAR<\/code> (which logically <em>should<\/em> be a typedef) is probably a macro that expands to something like <code>unsigned short<\/code> (using a 16-bit type because Windows likes to use 16-bit wide characters for UTF-16).<\/p>\n<p>So your definition:<\/p>\n<pre><code>int _tmain(int argc, _TCHAR* argv[])\n<\/code><\/pre>\n<p>expands to:<\/p>\n<pre><code>int _tmain(int argc, unsigned short* argv[])\n<\/code><\/pre>\n<p>which, because you&#8217;ve unintentionally redefined <code>unsigned<\/code>, then expands to:<\/p>\n<pre><code>int _tmain(int argc,  int uint32_t; short* argv[])\n<\/code><\/pre>\n<p>And since parameter declarations are separated by commas, not by semicolons, this is a syntax error. I&#8217;m not sure why this leads to the particular error message you&#8217;re seeing, but it&#8217;s not terribly surprising. Syntax errors, particularly those involving incorrectly defined macros, often lead to confusing error messages.<\/p>\n<p>The best strategy for something like this is <em>usually<\/em> to look at the <em>earliest<\/em> line on which the compiler reports an error. If the error message itself is not illuminating, ignore it and study the source, trying to figure out what you might have gotten wrong.<\/p>\n<p>If that fails (as it would in this case), try running your program through just the preprocessor. Most Unix-based compilers, including gcc, use a <code>-E<\/code> option for this; I don&#8217;t know the corresponding option for Microsoft. The output of the preprocessor is likely to be very verbose (it will include mangled copies of all the headers you include, directly or indirectly), but examining it might lead you to something useful.<\/p>\n<p>In this particular case, commenting out your <code>#define<\/code> directive would have made the error go away (<em>CORRECTION: no, it wouldn&#8217;t<\/em>), which would be a clue that there&#8217;s something wrong with the <code>#define<\/code>, even though the relationship between it and the error message is far from obvious.<\/p>\n<\/p><\/div>\n<div class=\"mt24\"><\/div>\n<\/div>\n<p>            <span class=\"d-none\" itemprop=\"commentCount\"><\/span> <\/p><\/div>\n<\/div>\n<p>[ad_2]<\/p>\n<p>solved Error\t2\terror C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int <\/p>\n","protected":false},"excerpt":{"rendered":"<p>[ad_1] This is actually a rather interesting error; the error message doesn&#8217;t do much to tell you what the problem is. My initial speculation was largely incorrect, but I&#8217;ve left it in place for now. See below. This code: #ifndef uint32_t #define unsigned int uint32_t; #endif is incorrect. The name of the macro being defined &#8230; <a title=\"[Solved] Error\t2\terror C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int\" class=\"read-more\" href=\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\" aria-label=\"More on [Solved] Error\t2\terror C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[320],"tags":[324],"class_list":["post-12112","post","type-post","status-publish","format-standard","hentry","category-solved","tag-c"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>[Solved] Error 2 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int - JassWeb<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"[Solved] Error 2 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int - JassWeb\" \/>\n<meta property=\"og:description\" content=\"[ad_1] This is actually a rather interesting error; the error message doesn&#8217;t do much to tell you what the problem is. My initial speculation was largely incorrect, but I&#8217;ve left it in place for now. See below. This code: #ifndef uint32_t #define unsigned int uint32_t; #endif is incorrect. The name of the macro being defined ... Read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\" \/>\n<meta property=\"og:site_name\" content=\"JassWeb\" \/>\n<meta property=\"article:published_time\" content=\"2022-09-29T11:22:50+00:00\" \/>\n<meta name=\"author\" content=\"Kirat\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kirat\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\"},\"author\":{\"name\":\"Kirat\",\"@id\":\"https:\/\/jassweb.com\/solved\/#\/schema\/person\/65c9c7b7958150c0dc8371fa35dd7c31\"},\"headline\":\"[Solved] Error 2 error C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int\",\"datePublished\":\"2022-09-29T11:22:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\"},\"wordCount\":857,\"publisher\":{\"@id\":\"https:\/\/jassweb.com\/solved\/#organization\"},\"keywords\":[\"c++\"],\"articleSection\":[\"Solved\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\",\"url\":\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\",\"name\":\"[Solved] Error 2 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int - JassWeb\",\"isPartOf\":{\"@id\":\"https:\/\/jassweb.com\/solved\/#website\"},\"datePublished\":\"2022-09-29T11:22:50+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/jassweb.com\/solved\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"[Solved] Error 2 error C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/jassweb.com\/solved\/#website\",\"url\":\"https:\/\/jassweb.com\/solved\/\",\"name\":\"JassWeb\",\"description\":\"Build High-quality Websites\",\"publisher\":{\"@id\":\"https:\/\/jassweb.com\/solved\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/jassweb.com\/solved\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/jassweb.com\/solved\/#organization\",\"name\":\"Jass Web\",\"url\":\"https:\/\/jassweb.com\/solved\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/jassweb.com\/solved\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/jassweb.com\/wp-content\/uploads\/2021\/02\/jass-website-logo-1.png\",\"contentUrl\":\"https:\/\/jassweb.com\/wp-content\/uploads\/2021\/02\/jass-website-logo-1.png\",\"width\":693,\"height\":132,\"caption\":\"Jass Web\"},\"image\":{\"@id\":\"https:\/\/jassweb.com\/solved\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/jassweb.com\/solved\/#\/schema\/person\/65c9c7b7958150c0dc8371fa35dd7c31\",\"name\":\"Kirat\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/jassweb.com\/solved\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/jassweb.com\/solved\/wp-content\/litespeed\/avatar\/1261af3c9451399fa1336d28b98ea3bb.jpg?ver=1775798750\",\"contentUrl\":\"https:\/\/jassweb.com\/solved\/wp-content\/litespeed\/avatar\/1261af3c9451399fa1336d28b98ea3bb.jpg?ver=1775798750\",\"caption\":\"Kirat\"},\"sameAs\":[\"http:\/\/jassweb.com\"],\"url\":\"https:\/\/jassweb.com\/solved\/author\/jaspritsinghghumangmail-com\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"[Solved] Error 2 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int - JassWeb","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/","og_locale":"en_US","og_type":"article","og_title":"[Solved] Error 2 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int - JassWeb","og_description":"[ad_1] This is actually a rather interesting error; the error message doesn&#8217;t do much to tell you what the problem is. My initial speculation was largely incorrect, but I&#8217;ve left it in place for now. See below. This code: #ifndef uint32_t #define unsigned int uint32_t; #endif is incorrect. The name of the macro being defined ... Read more","og_url":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/","og_site_name":"JassWeb","article_published_time":"2022-09-29T11:22:50+00:00","author":"Kirat","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kirat","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/#article","isPartOf":{"@id":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/"},"author":{"name":"Kirat","@id":"https:\/\/jassweb.com\/solved\/#\/schema\/person\/65c9c7b7958150c0dc8371fa35dd7c31"},"headline":"[Solved] Error 2 error C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int","datePublished":"2022-09-29T11:22:50+00:00","mainEntityOfPage":{"@id":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/"},"wordCount":857,"publisher":{"@id":"https:\/\/jassweb.com\/solved\/#organization"},"keywords":["c++"],"articleSection":["Solved"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/","url":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/","name":"[Solved] Error 2 error C4430: missing type specifier - int assumed. Note: C++ does not support default-int - JassWeb","isPartOf":{"@id":"https:\/\/jassweb.com\/solved\/#website"},"datePublished":"2022-09-29T11:22:50+00:00","breadcrumb":{"@id":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/jassweb.com\/solved\/solved-error2error-c4430-missing-type-specifier-int-assumed-note-c-does-not-support-default-int\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/jassweb.com\/solved\/"},{"@type":"ListItem","position":2,"name":"[Solved] Error 2 error C4430: missing type specifier &#8211; int assumed. Note: C++ does not support default-int"}]},{"@type":"WebSite","@id":"https:\/\/jassweb.com\/solved\/#website","url":"https:\/\/jassweb.com\/solved\/","name":"JassWeb","description":"Build High-quality Websites","publisher":{"@id":"https:\/\/jassweb.com\/solved\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jassweb.com\/solved\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/jassweb.com\/solved\/#organization","name":"Jass Web","url":"https:\/\/jassweb.com\/solved\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jassweb.com\/solved\/#\/schema\/logo\/image\/","url":"https:\/\/jassweb.com\/wp-content\/uploads\/2021\/02\/jass-website-logo-1.png","contentUrl":"https:\/\/jassweb.com\/wp-content\/uploads\/2021\/02\/jass-website-logo-1.png","width":693,"height":132,"caption":"Jass Web"},"image":{"@id":"https:\/\/jassweb.com\/solved\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/jassweb.com\/solved\/#\/schema\/person\/65c9c7b7958150c0dc8371fa35dd7c31","name":"Kirat","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/jassweb.com\/solved\/#\/schema\/person\/image\/","url":"https:\/\/jassweb.com\/solved\/wp-content\/litespeed\/avatar\/1261af3c9451399fa1336d28b98ea3bb.jpg?ver=1775798750","contentUrl":"https:\/\/jassweb.com\/solved\/wp-content\/litespeed\/avatar\/1261af3c9451399fa1336d28b98ea3bb.jpg?ver=1775798750","caption":"Kirat"},"sameAs":["http:\/\/jassweb.com"],"url":"https:\/\/jassweb.com\/solved\/author\/jaspritsinghghumangmail-com\/"}]}},"_links":{"self":[{"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/posts\/12112","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/comments?post=12112"}],"version-history":[{"count":0,"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/posts\/12112\/revisions"}],"wp:attachment":[{"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/media?parent=12112"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/categories?post=12112"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jassweb.com\/solved\/wp-json\/wp\/v2\/tags?post=12112"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}