Just write some simple, "Hello, world!"-class, example. Without such specifics the whole idea is just too vague and open-ended.
We have already published much more than "hello world" examples of AT (
http://ciyam.org/at) and the first ACCT (Atomic Cross-Chain Transfer) between two separate blockchains (Qora and Burst) has already happened.
I could not find any C++ example in your documentation directory. All examples were tabulated assembly listings. I wanted to see your vision on how C++ will improve the situation for a programming user or a financial service developer. I honestly lack this insight.
Do you seriously think we don't have a product that works?
What I'm seriously thinking is that you are similar to some newfangled hardware microprocessor developers from Europe that I've met in the past. They had their architecture, they had their assembler and simulations. They even had real silicon implementations in structured ASIC. But when no further investments were forthcoming they decided that they need open source GNU toolchain and an IDE based on Eclipse. And that was where they went bankrupt, got acquired and forced to realign their design with real market demands.
Really, instead of posting one-liners, please sit down and write a nice position paper that has your atomic cross-chain transfer recoded in your intended dialect of C++. Something like the listing below will showcase your ideas much better that what you are currently doing.
; Listing generated by Microsoft (R) Optimizing Compiler Version 17.00.50727.1
.model flat
_DATA SEGMENT
$SG1297 DB 'Hello, world!', 00H
_DATA ENDS
PUBLIC _main
EXTRN _puts:PROC
; Function compile flags: /Odtp
; File c:\users\2112\hello.c
_TEXT SEGMENT
_argc$ = 8 ; size = 4
_argv$ = 12 ; size = 4
_main PROC
; 1 : int main(int argc,char **argv) {
00000 55 push ebp
00001 8b ec mov ebp, esp
; 2 : return puts("Hello, world!");
00003 68 00 00 00 00 push OFFSET $SG1297
00008 e8 00 00 00 00 call _puts
0000d 83 c4 04 add esp, 4
; 3 : }
00010 5d pop ebp
00011 c3 ret 0
_main ENDP
_TEXT ENDS
END
Edit: I just realized that a code listing example using the venerable Intel x86 architecture is too readable, people are too familiar with it and it was designed to be hand-programmed in assembly and therefore has nice mnemonic register names. To make a fairer comparison with AT I produced the same listing with ARM/THUMB compiler. This should better reproduce the level of confusion and discomfort that one would encounter with a completely new machine architecture like AT.
; Listing generated by Microsoft (R) Optimizing Compiler Version 17.00.50727.1
00000 AREA |.data|, DATA
|$SG619| DCB "Hello, world!", 0x0
EXPORT |main|
IMPORT |puts|
00000 AREA |.pdata|, PDATA
|$pdata1$main| DCD imagerel |$LN5@main|
DCD imagerel |$unwind2$main|
00000 AREA |.xdata|, DATA
|$unwind2$main| DCD 0x33200011
DCD 0xa8fb02
DCD 0x8802ff02
DCD 0xff03ef00
; Function compile flags: /Odsp
; File c:\users\2112\hello.c
00000 AREA |.text|, CODE, THUMB
00000 |main| PROC
; 1 : int main(int argc,char **argv) {
00000 |$LN5@main|
00000 b403 push {r0,r1}
00002 e92d 4800 push {r11,lr}
00006 46eb mov r11,sp
00008 b082 sub sp,sp,#8
0000a |$M3|
; 2 : return puts("Hello, world!");
0000a 4806 ldr r0,|$LN8@main| ; =|$SG619|
0000c f000 f800 bl puts
00010 9000 str r0,[sp]
00012 9b00 ldr r3,[sp]
00014 9301 str r3,[sp,#4]
; 3 : }
00016 9801 ldr r0,[sp,#4]
00018 |$M6|
00018 b002 add sp,sp,#8
0001a f85d bb04 pop {r11}
0001e f85d fb0c ldr pc,[sp],#0xC
00022 |$M9|
00022 defe __debugbreak
00024 |$LN7@main|
00024 |$LN8@main|
00024 0000 0000 DCD |$SG619|
00028 |$M4|
ENDP ; |main|
END
