Difference between revisions of "BlackBox Component Builder 1.7"
Josef templ (talk | contribs) (→UTF8) |
Josef templ (talk | contribs) |
||
| Line 29: | Line 29: | ||
<code>inaddr := SYSTEM.VAL(WinNet.in_addr, hostentry.h_addr_list^[0]^)</code> | <code>inaddr := SYSTEM.VAL(WinNet.in_addr, hostentry.h_addr_list^[0]^)</code> | ||
=== Underlined | === Underlined white space === | ||
Underlined spaces and tabs are now shown according to the defined format, i.e. they are underlined. So we recommend you to check your documentation files and/or program generated text files to prevent unexpected underlines. | |||
=== UTF8 === | === UTF8 === | ||
Revision as of 07:32, 26 April 2016
Download beta version
Migration from 1.6
There is the tool for batch compilation of subsystems: ypkDevTool.
The several typical changes you should do for adopting your subsystems for 1.7 are listed bellow:
IN to VAR
Now it is forbidden to call method of argument variable marked out by IN. You should change this flag to VAR.
Read-only variables
With 1.7 you can not call the method of read-only variable object in other module. So you should export such variable by *.
WinNet
WinNet.hostnet definition was changed, so you need to replace:
inaddr := hostentry.h_addr_list^[0]^[0]
to
inaddr := SYSTEM.VAL(WinNet.in_addr, hostentry.h_addr_list^[0]^)
Underlined white space
Underlined spaces and tabs are now shown according to the defined format, i.e. they are underlined. So we recommend you to check your documentation files and/or program generated text files to prevent unexpected underlines.
UTF8
UTF-8 conversion supported "out of the box" from module Strings. So if you are using UTF-8 conversions embedded in your own code or from some third-party modules, you can switch to the new Strings procedures.
External calls
1.7 supports calling URLs and Emails so now you can be sure, that user can call your link from documentation even if Info or i21Sys subsystem does not installed.
Use Dialog.OpenExternal procedure to call URLs.