For students who study 1C Mobile course.

#1
People who like this: 0 Yes / 0 No
Active user
Rating: 3
Joined: Jan 11, 2021
Company: Robot cho mọi người

Hi everyone,
I've downloaded a sample infobase from the course. I saw many line in the code have no ";" and the code have no syntax error. My question is do we need ";" in a procedure with ony 1 line of code.

 
#2
People who like this: 0 Yes / 0 No
Active user
Rating: 3
Joined: Jan 11, 2021
Company: Robot cho mọi người

 
#3
People who like this: 0 Yes / 0 No
Active user
Rating: 3
Joined: Jan 11, 2021
Company: Robot cho mọi người

 
#4
People who like this: 0 Yes / 0 No
Administrator
Rating: 29
Joined: Oct 3, 2019
Company:

Hello Phan Hoàng Anh,

this is such a feature of the current version of the 1C language that in a procedure with one line the symbol ";" not needed. There will be no error in this case.

Also, there will be no error if you don't put the ";" at the end of a multi-line procedure:

Code
Procedure SaveStory(SystemAnswer, Command, MessageID)
   
   RecordManager    = InformationRegisters.MessageHistory.CreateRecordManager();
   
   RecordManager.Period       = CurrentDate();
   RecordManager.Message       = SystemAnswer;
   RecordManager.Command       = Command;
   RecordManager.KindMessage    = Enums.KindsMessage.Outcoming;
   RecordManager.ID_Message    = MessageID;
   
   RecordManager.Write(True)//;
   
EndProcedure


My advice: always use the ";" no matter how many lines there're in your procedures. This will allow you to maintain the compatibility of your applications in the future if this feature is removed in new versions of the language.

 
#5
People who like this: 0 Yes / 0 No
Active user
Rating: 3
Joined: Jan 11, 2021
Company: Robot cho mọi người

Thanks for your support

 
Subscribe
Users browsing this topic (guests: 1, registered: 0, hidden: 0)
Be the first to know tips & tricks on business application development!

A confirmation e-mail has been sent to the e-mail address you provided .

Click the link in the e-mail to confirm and activate the subscription.

/* Улучшаем читаемость списков в документации */ .workarea ul, .content ul { margin: 15px 0 20px 25px !important; padding: 0 !important; list-style-type: disc !important; } .workarea li, .content li { margin-bottom: 8px !important; padding-left: 5px !important; line-height: 1.6 !important; } /* Ультимативный фикс для всех уровней заголовков в контенте */ .workarea h1, .workarea h2, .workarea h3, .workarea h4, .workarea h5, .workarea h6, .content h1, .content h2, .content h3, .content h4, .content h5, .content h6, div[id*="content"] h5, div[class*="content"] h5 { display: block !important; font-weight: 700 !important; color: #005aa0 !important; /* Наш фирменный синий */ text-transform: none !important; margin-top: 30px !important; margin-bottom: 15px !important; line-height: 1.2 !important; font-family: Arial, sans-serif !important; } /* Принудительные размеры в пикселях (чтобы не зависеть от % или em) */ .workarea h1, .content h1 { font-size: 28px !important; } .workarea h2, .content h2 { font-size: 24px !important; } .workarea h3, .content h3 { font-size: 21px !important; } .workarea h4, .content h4 { font-size: 19px !important; } .workarea h5, .content h5 { font-size: 18px !important; } /* Для 5 решеток ##### */ .workarea h6, .content h6 { font-size: 16px !important; } /* Фикс, если Битрикс добавил лишние отступы перед списками после заголовка */ .workarea h5 + ul, .content h5 + ul { margin-top: 5px !important; }