My ChatGPT+Gemini coding Experiments

[daydreamer]

JJ showed earlier a perfect English to swedish ChatGPT translation
Example of errors in Google translate, example is
Trial by fire = "eldprov", the main character that is a mage is tested by their master mage
But Google translate "trial" as it's used in court when some criminal stand trial in court for crime committed

[daydreamer]

chatgpt made a perfect swedish translation of my fantasy story part "trial by fire" 

[daydreamer]

I wrote several .doc files in english as parts of my fantasy novel and desided to translate it to swedish,for those who dont understand english
Google translate was dissppointment,chatgpt might do better ?

Well, try it and let us know. (It's free, innit?)
Or you could try DeepSeek.

It worked much better than google translate
chatgpt intelligently understand word meaning different depending on in which context its used,while google translate seem more translate word by word,dont care about which context its used in

Wonder anyone interesting in reading my fantasy story and give feedback ?

[daydreamer]

I remember i have old copy of ms office,gonna try install publisher,which helps you print out small books which you fokd oages to half size of A4 to A5 book size,keeping track of page numbers to end up in right places

[jj2007]

ChatGPT gave me this C++ example for using GdipAddPathPath, but it throws plenty of cryptic errors:

Code Select Expand

#include <windows.h>
#include <gdiplus.h>
#pragma comment (lib,"Gdiplus.lib")

using namespace Gdiplus;

LRESULT CALLBACK WndProc(HWND, UINT, WPARAM, LPARAM);

int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
{
    // Initialize GDI+
    GdiplusStartupInput gdiplusStartupInput;
    ULONG_PTR gdiplusToken;
    GdiplusStartup(&gdiplusToken, &gdiplusStartupInput, NULL);

    // Register Window Class
    WNDCLASS wc = { 0 };
    wc.lpfnWndProc = WndProc;
    wc.hInstance = hInstance;
    wc.lpszClassName = L"GDIPlusExample";
    RegisterClass(&wc);

    // Create Window
    HWND hwnd = CreateWindow(L"GDIPlusExample", L"GDI+ Path Example",
        WS_OVERLAPPEDWINDOW, CW_USEDEFAULT, CW_USEDEFAULT,
        800, 600, NULL, NULL, hInstance, NULL);

    ShowWindow(hwnd, nCmdShow);
    UpdateWindow(hwnd);

    // Message Loop
    MSG msg;
    while (GetMessage(&msg, NULL, 0, 0))
    {
        TranslateMessage(&msg);
        DispatchMessage(&msg);
    }

    // Shutdown GDI+
    GdiplusShutdown(gdiplusToken);
    return (int)msg.wParam;
}

// Window Procedure
LRESULT CALLBACK WndProc(HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam)
{
    switch (message)
    {
    case WM_PAINT:
    {
        PAINTSTRUCT ps;
        HDC hdc = BeginPaint(hwnd, &ps);

        // Create GDI+ Graphics object
        Graphics graphics(hdc);

        // Create two paths
        GpPath* path1;
        GpPath* path2;
        GdipCreatePath(FillModeWinding, &path1);
        GdipCreatePath(FillModeWinding, &path2);

        // Add a rectangle to path1
        GdipAddPathRectangle(path1, 100, 100, 200, 150);

        // Add an ellipse to path2
        GdipAddPathEllipse(path2, 200, 150, 200, 150);

        // Merge path2 into path1, connecting with a line
        GdipAddPathPath(path1, path2, TRUE);

        // Create a pen and draw the merged path
        GpPen* pen;
        GdipCreatePen1(Color::Red, 3, UnitPixel, &pen);
        GdipDrawPath((GpGraphics*)&graphics, pen, path1);

        // Cleanup
        GdipDeletePen(pen);
        GdipDeletePath(path1);
        GdipDeletePath(path2);

        EndPaint(hwnd, &ps);
    }
    break;

    case WM_DESTROY:
        PostQuitMessage(0);
        return 0;
    }
    return DefWindowProc(hwnd, message, wParam, lParam);
}

Does it compile for someone?

[daydreamer]

Different Version of gdiplus causes many errors ?
Never seen #pragma before used in CPP

[TimoVJL]

A test code for Pelles C
Don't work yet

Code Select Expand

#define UNICODE
#define WIN32_LEAN_AND_MEAN
#include <windows.h>
//#include <gdiplusFlat.h>
#pragma comment (lib,"Gdiplus.lib")

//using namespace Gdiplus;
// GdiPlusFlat.h

#define WINGDIPAPI __stdcall
#define GDIPCONST const

typedef enum
{
    FillModeAlternate,        // 0
    FillModeWinding          // 1
} GpFillMode;

typedef enum
{
    UnitWorld,      //<! 0 = World coordinate (non-physical unit)
    UnitDisplay,    //<! 1 = Variable -- for PageTransform only
    UnitPixel,      //<! 2 = Each unit is one device pixel.
    UnitPoint,      //<! 3 = Each unit is a printer's point, or 1/72 inch.
    UnitInch,      //<! 4 = Each unit is 1 inch.
    UnitDocument,  //<! 5 = Each unit is 1/300 inch.
    UnitMillimeter  //<! 6 = Each unit is 1 millimeter.
} GpUnit;

typedef struct
{
    UINT32 GdiplusVersion ;
    void* DebugEventCallback ;
    BOOL SuppressBackgroundThread ;
    BOOL SuppressExternalCodecs ;
} GdiplusStartupInput ;

typedef float REAL;
typedef DWORD ARGB;

typedef struct tagGpGraphics GpGraphics;
typedef struct tagGpPath GpPath;
typedef struct tagGpPen GpPen;


typedef struct
{
    void* NotificationHook;    //NotificationHookProc NotificationHook;
    void* NotificationUnhook;    //NotificationUnhookProc NotificationUnhook;
} GdiplusStartupOutput ;

int __stdcall GdiplusStartup(ULONG_PTR*, const GdiplusStartupInput*, GdiplusStartupOutput*) ;
void __stdcall GdiplusShutdown(ULONG_PTR) ;
int __stdcall GdipCreatePath(GpFillMode brushMode, GpPath **path);
int __stdcall GdipAddPathRectangle(GpPath *path, REAL x, REAL y, REAL width, REAL height);
int __stdcall GdipAddPathEllipse(GpPath *path, REAL x, REAL y, REAL width, REAL height);
int __stdcall GdipAddPathPath(GpPath *path, GDIPCONST GpPath* addingPath, BOOL connect);
int __stdcall GdipCreatePen1(ARGB color, REAL width, GpUnit unit, GpPen **pen);
int __stdcall GdipDrawPath(GpGraphics *graphics, GpPen *pen, GpPath *path);
int __stdcall GdipDeletePath(GpPath* path);
int __stdcall GdipDeletePen(GpPen *pen);
int __stdcall GdipCreateFromHDC(HDC hdc, GpGraphics **graphics);
int __stdcall GdipDeleteGraphics(GpGraphics *graphics);

LRESULT CALLBACK WndProc(HWND, UINT, WPARAM, LPARAM);

int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow)
{
    // Initialize GDI+
    GdiplusStartupInput gdiplusStartupInput = {1,0,0,0};
    ULONG_PTR gdiplusToken;
    GdiplusStartup(&gdiplusToken, &gdiplusStartupInput, NULL);

    // Register Window Class
    WNDCLASS wc = { 0 };
    wc.style = CS_HREDRAW | CS_VREDRAW;
    wc.lpfnWndProc = WndProc;
    wc.hInstance = hInstance;
    wc.lpszClassName = L"GDIPlusExample";
    RegisterClass(&wc);

    // Create Window
    HWND hwnd = CreateWindow(L"GDIPlusExample", L"GDI+ Path Example",
        WS_OVERLAPPEDWINDOW, CW_USEDEFAULT, CW_USEDEFAULT,
        800, 600, NULL, NULL, hInstance, NULL);

    ShowWindow(hwnd, nCmdShow);
    //UpdateWindow(hwnd);

    // Message Loop
    MSG msg;
    while (GetMessage(&msg, NULL, 0, 0))
    {
        TranslateMessage(&msg);
        DispatchMessage(&msg);
    }

    // Shutdown GDI+
    GdiplusShutdown(gdiplusToken);
    return (int)msg.wParam;
}

// Window Procedure
LRESULT CALLBACK WndProc(HWND hwnd, UINT message, WPARAM wParam, LPARAM lParam)
{
    switch (message)
    {
    case WM_PAINT:
    {
        PAINTSTRUCT ps;
        HDC hdc = BeginPaint(hwnd, &ps);

        // Create GDI+ Graphics object
        //Graphics graphics(hdc);
        GpGraphics *graphics;
        GdipCreateFromHDC(hdc, &graphics);

        // Create two paths
        GpPath* path1;
        GpPath* path2;
        GdipCreatePath(FillModeWinding, &path1);
        GdipCreatePath(FillModeWinding, &path2);

        // Add a rectangle to path1
        GdipAddPathRectangle(path1, 100.0, 100.0, 200.0, 150.0);

        // Add an ellipse to path2
        GdipAddPathEllipse(path2, 200.0, 150.0, 200.0, 150.0);

        // Merge path2 into path1, connecting with a line
        GdipAddPathPath(path1, path2, TRUE);

        // Create a pen and draw the merged path
        GpPen* pen;
        GdipCreatePen1(0xFFFF0000, 3.0, UnitPixel, &pen);
        GdipDrawPath(graphics, pen, path1);

        // Cleanup
        GdipDeletePen(pen);
        GdipDeletePath(path1);
        GdipDeletePath(path2);
        GdipDeleteGraphics(graphics);

        EndPaint(hwnd, &ps);
    }
    break;

    case WM_DESTROY:
        PostQuitMessage(0);
        return 0;
    }
    return DefWindowProc(hwnd, message, wParam, lParam);
}


[ognil]

I always ask the same question to 5 AIs and choose the best answer.    

To demonstrate how to use GdipAddPathPath and GdipDrawPath in MASM64 (Microsoft Macro Assembler for 64-bit), we need to first understand the purpose of these functions:

GdipAddPathPath : This function adds one path to another path. It is useful when you want to combine multiple paths into a single path object.

GdipDrawPath : This function draws a path on a graphics object using a specified pen.
Below is an example of how to use these functions in MASM64. The example assumes you have already set up GDI+ in your program, including initializing the GDI+ library and creating a graphics object.

Step-by-Step Explanation

Initialize GDI+ : Before using any GDI+ functions, you must initialize the GDI+ library.
Create Graphics and Paths : Create a Graphics object from a device context (e.g., a window or bitmap) and create two Path objects.

Add Paths : Use GdipAddPathPath to combine the two paths into one.
Draw the Combined Path : Use GdipDrawPath to render the combined path on the graphics object.

Clean Up : Release all GDI+ resources and shut down the library.

Example Code
asm

Code Select Expand

include \masm32\include64\masm64rt.inc
include \masm32\include64\gdiplus.inc
includelib \masm32\lib64\kernel32.lib
includelib \masm32\lib64\user32.lib
includelib \masm32\lib64\gdiplus.lib

; GDI+ Startup Input structure
GdiplusStartupInput STRUCT
    GdiplusVersion            DWORD ?
    DebugEventCallback        QWORD ?
    SuppressBackgroundThread  BOOL ?
    SuppressExternalCodecs    BOOL ?
GdiplusStartupInput ENDS

; Data segment
.data
hWnd                QWORD 0
hDC                 QWORD 0
graphics            QWORD 0
path1               QWORD 0
path2               QWORD 0
combinedPath        QWORD 0
pen                 QWORD 0
token               QWORD 0
startupInput        GdiplusStartupInput <1, 0, FALSE, FALSE>

; Code segment
.code
WinMain proc
    ; Initialize GDI+
    invoke GdiplusStartup, addr token, addr startupInput, 0
    .if eax != 0
        invoke ExitProcess, 1
    .endif
    ; Obtain a handle to the window and its device context
    invoke GetConsoleWindow
    mov hWnd, rax
    invoke GetDC, hWnd
    mov hDC, rax
    ; Create a Graphics object from the device context
    invoke GdipCreateFromHDC, hDC, addr graphics
    .if eax != 0
        invoke GdiplusShutdown, token
        invoke ExitProcess, 1
    .endif
    ; Create two Path objects
    invoke GdipCreatePath, 0, addr path1
    invoke GdipCreatePath, 0, addr path2
    ; Add shapes to the paths
    ; Path 1: A rectangle
    invoke GdipAddPathRectangle, path1, 50, 50, 100, 100
    ; Path 2: A circle
    invoke GdipAddPathEllipse, path2, 100, 100, 100, 100
    ; Combine the two paths into a new path
    invoke GdipCreatePath, 0, addr combinedPath
    invoke GdipAddPathPath, combinedPath, path1, TRUE
    invoke GdipAddPathPath, combinedPath, path2, TRUE
    ; Create a Pen for drawing
    invoke GdipCreatePen1, 0xFF0000FFh, 2, 2, addr pen
    ; Draw the combined path
    invoke GdipDrawPath, graphics, pen, combinedPath
    ; Clean up
    invoke GdipDeletePath, path1
    invoke GdipDeletePath, path2
    invoke GdipDeletePath, combinedPath
    invoke GdipDeletePen, pen
    invoke GdipDeleteGraphics, graphics
    invoke ReleaseDC, hWnd, hDC
    invoke GdiplusShutdown, token
    ; Exit the program
    invoke ExitProcess, 0
WinMain endp
endKey Points in the Code

Initialization :
GdiplusStartup initializes the GDI+ library.
GetConsoleWindow and GetDC retrieve the handle to the console window and its device context.

Creating Paths :
GdipCreatePath creates two empty paths (path1 and path2).
GdipAddPathRectangle and GdipAddPathEllipse add shapes to the paths.

Combining Paths :
GdipAddPathPath combines path1 and path2 into combinedPath.

Drawing :
GdipCreatePen1 creates a pen with a blue color (0xFF0000FFh).
GdipDrawPath renders the combined path on the graphics object.

Cleanup :
All created objects are deleted using their respective GdipDelete* functions.
ReleaseDC releases the device context, and GdiplusShutdown shuts down the GDI+ library.

Notes
Error Handling : In a production environment, you should check the return values of all GDI+ functions to ensure they succeed.

Linking : Ensure that you link against gdiplus.lib and include the appropriate headers.

Dependencies : This example assumes you have the MASM64 environment set up with GDI+ support.
This example demonstrates the basic usage of GdipAddPathPath and GdipDrawPath in MASM64. You can extend it by adding more complex shapes, transformations, or additional drawing operations.

[jj2007]

I know all this, Lingo. In fact, I do have a perfectly working example. Problem is I have a second example that gives me a runtime error, and I don't have the faintest idea why.

[jj2007]

A test code for Pelles C

Compiles without errors but shows only a white screen... thanks anyway, Timo

[TimoVJL]

A test code for Pelles C

Compiles without errors but shows only a white screen... thanks anyway, Timo

It was just a conversion from bad AI code, nothing else.
EDIT: one cast error fixed, so now it draw path

[zedd151]

Regarding any AI model that produces code... either C or assembly...

You must check and verify. The code produced may, and often does, contain errors.

This much I found out for myself.

My experience was that only 25% of code generated by AI actually compiled/assembled without error, runs without crashing,  and actually produced the correct outcome or results.

Your mileage may vary. 
I discontinued my own AI experimentation, in this context, after only a few days.

I had noticed that ChatGPT (iirc) at least, had stopped giving me assembly code that uses the irvine32 libraries. 
The C code it had generated usually compiled fine with gcc, except for some that had errors that caused compiler or linking issues. I had not tried compiling with any MS compiler.

The more complex the criteria, the more error prone was the resulting generated code in most cases.

Also, AI was prone to addressing errors like "mov eax, [esi+ecx*9]" or similar addressing errors. 

[daydreamer]

well earlier I tested with question "can you translate this to swedish?" with chatgpt
knowing there is specific differences between American English and British English and other countries english,so if I want to translate some text from british tv shows,might need to be more specific ?

nobody tried to ask one of the AI's "can you debug this cpp code for me?" yet?
or tried more specific question where you ask about visual cpp or your choice of compiler ?

[zedd151]

nobody tried to ask one of the AI's "can you debug this cpp code for me?" yet?
or tried more specific question where you ask about visual cpp or your choice of compiler ?

The more complex the task that any AI model is given, the error rate increases somewhat proportionally I would assume, or even exponentially.

cpp (or C++) in any form, is more complex than simple plain old C.
Plus there are differences in cpp for gnu c compiler, and c++ for Microsoft  VisualC++, which would tend to add to the complexity.

One size does not fit all in this instance.  Not that I have any great knowledge of any variety of cpp or C++ nor do I claim any fluency in either, or plain C for that matter.    The only thing that I do know, is that it is way easier to port C code to assembly, than porting any variety of cpp/c++ code to assembly. I briefly looked into doing that.

Maybe in 5 or 10 years (or more?) AI will be able to reliably produce code in the most used formats/languages, and even some seldom used formats/languages.

All of these are my very, very humblest of opinions of course. 
Mileage may vary, depending on how well any request to the AI model is articulated.  A key point it seems, when asking anything from AI. 

Now making grammatically correct translations from one language to another possibly 'localized' language (English for example, US English, AU English and the Queens English {UK}), and vice versa, is another can of worms, and somewhat beyond the scope of the original intent of this topic.  I have been told that many countries, by the way, allegedly speak/read/write the same language as The United States. Some of which needs translation to American English. 

I hereby reserve the right to mis-speak, or even have views that might deviate from that of other folks, etc., etc., blah, blah, blah, ad nauseum.    Meaning some of what is written here could be wrong, or misguided or misinterpreted.    The latter parts obviously meant tongue in cheek.

[ognil]

I know all this, Lingo. In fact, I do have a perfectly working example.

Thank you Duce,
You are welcome.