[Zdavir Muhammad]

Zdavir, when people ask you to put CODE delimiters around Stata code (or output), this is what they are talking about (copied from the FAQ).

---

12.3 How to use CODE delimiters

Stata code (i.e. the exact commands issued) is very much easier to read if presented as such.

When you are editing an answer you should see a # button in the toolbar above the text area. Click on # to insert

 and

mark-up. Write your code between, paying particular attention to linebreaks and indentation.

If you do not see that button, then click on the “Toggle Advanced Editor” button (an underlined A) in the area above to show the toolbar.

If you do not have access to the Advanced Editor in your interface, you can just insert those mark-ups manually before, or indeed after, you insert your code. Many people fast at typing do that any way.

Examples of your data (or of realistic similar datasets) are also much easier to read if presented as CODE. dataex, explained just above, automatically generates text including CODE delimiters, which can be copied and pasted into Statalist posts.

What is valuable with presenting code or data as CODE is that other members can easily copy and paste what you post to play with in their Stata installation.

---

Cheers,
Bruce

Im sorry, sir. Im having some trouble to understand with your statement because of my lack of advance english that i have

If you could show me with some video on Youtube channel i would be very grateful for your point and understanding your statement with little more easy for me

[Zdavir Muhammad]

for run hettest on RE model could we use xtgls command, sir?