Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

AI may help us to create plugins

(1/2) > >>

ollydbg:
Hi, I recently see a website named deepwiki, this site can read a github project, and later, it can have LLM powered AI chat about this project. As a test, I just put the code::blocks' source code to the index, see: https://deepwiki.com/asmwarrior/codeblocks_sfmirror

After that, I just wrote some text to AI:

can you help me to create a code::blocks plugin which can run the memory leak detector mentioned here: https://github.com/ssbssa/heob

And I see that it can create the source code for this plugin, looks interesting.  :)

christo:
Generated wiki looks nice, I'm hearing about deepwiki first time, looks very useful tool. Thank you for sharing.

Regarding the plugin generated, how complete was the code?

ollydbg:

--- Quote from: christo on November 01, 2025, 06:22:53 am ---Generated wiki looks nice, I'm hearing about deepwiki first time, looks very useful tool. Thank you for sharing.

Regarding the plugin generated, how complete was the code?

--- End quote ---

I'm also new to d :)eepwiki site.

I haven't tried the generated code yet, but you can see this page:

https://deepwiki.com/search/can-you-help-me-to-create-a-co_35be54bd-5f47-4e3b-ba7d-bdff22584a0e

Just scroll down to the bottom of the page, it has many source code generated, and the code looks good.

Михаил Агарков:

--- Quote from: nate_higgers on November 03, 2025, 02:43:58 pm ---Well no kidding?! Who would've thunk?!
You know what could help us create plugins? Or create anything at all? Capable programmers.
This isn't helping. What's even the point of bringing up that crap? Seriously.
Look at the state of this project. How many people have been contributing? How many stable releases in the past eight years?
Last thing we need is incompetent scum "contributing" computer-generated garbage to any part of Code::Blocks. 
Well, if you guys want to kill it, then go ahead, suggest AI usage -- nay, even better, make AI plugins, an assistant on the IDE itself. A COPILOT integrated to it! Imagine that! Wouldn't that be great?
And not long ago we didn't even have a functional Symbols Browser. To be removed completely on a newer release. What a joke.
And people wonder why some things are as they are.
Listen to yourself, look around you, look at the project, look around it, then listen to yourself again, and think.
And you just threw Code::Blocks' source code into some garbage bin? Really, projects must have some sort of protection against this kind of stupidity, these days.
Then again, I don't know what's the goal exactly, but, if you guys are planning to turn this into a huge pile of crap, then disregard what I'm saying.
Thanks.
:)

--- End quote ---

Despite the slightly agressive response, I fully agree that AI is ruining a lot of things, e.g. localhost being broken in Windows 11 and worse.
The reason I love Code::Blocks is that it doesn't use overbloated JS frameworks with Electron, it uses native GUI controls and has a very nice feature set, like wxSmith and so much more.
I also don't want Code::Blocks to fallback on using AI to generate code, because it would very likely break things, god forbid it from using web technologies and take up hundreds of megabytes of RAM being idle just to have Copilot. I love this IDE because it just works, has an amazing feature set and can even work on Windows XP and ReactOS with no lag on old hardware.
If it were to introduce AI, I would very likely create a hard fork just for myself and anyone else interested.

blauzahn:
I'd also vote against, regardless of how tempting it might sound.

Using AI as inspiration or as lightning quick "seems to work" hack is fine as long as you resist the huge temptation to cut-copy-paste any single line of code you do not fully understand. Remember: As soon as you change/add anything, the responsability and maintenance becomes essentially yours, not the AI's.

Before adding yet more cruft, I'd favour fixing bugs in cb.

Finding potential memory leaks in cb can be done on Linux with e.g. cppcheck, scan-build, heaptrack or valgrind --- or just look for raw new in the editor and you'll quickly find a few good candidates.
Use a more modern programming style and you put in hardly any leak in the first place. Granted, legacy frameworks may limit its scope.

Navigation

[0] Message Index

[#] Next page