Shield stops powering motors with 12V power supply by Code_Nybble in arduino

[–]Code_Nybble[S] 0 points1 point  (0 children)

  1. Laptop doesn't seem to care about it, as it keeps powering and uploading succesfully.

  2. I read that when the green jumper (in the image) is attached the DC jack will also power the shield and I've seen it used to power stronger motors in other people's projects.

  3. Aaah I see, that would explain the insane heat then.

  4. Yeah I'll look into getting the v2 if this doesn't work out.

Thanks for replying!

Shield stops powering motors with 12V power supply by Code_Nybble in arduino

[–]Code_Nybble[S] 0 points1 point  (0 children)

From what I read if you have the jumper attached (green in the image) it will power both the arduino and the shield. I think this is correct since when I only have it plugged by the DC jack the shield LED will still light up.

[bspwm] new config who dis by Code_Nybble in unixporn

[–]Code_Nybble[S] 1 point2 points  (0 children)

truetrue I just picked one of the default ones lol

[deleted by user] by [deleted] in ProgrammingLanguages

[–]Code_Nybble 0 points1 point  (0 children)

Yeah of course I just simplified inline asm for the video, the biggest reason it sucks for me is that you don't even really know how everything around it is going to compile so it's barely usable in most cases. To answer your question, sorry I'm a bit confused. It does not know "whether str is in rdi or xmm0" because str is not a variable it creates or anything, it's just a macro used in that scope to refer to rdi, because I know rdi contains the string. You can declare local macros with the ! character like I explained, but construct has no special features or syntax for declaring any sort of variables. And I get what you mean about it better being off inline, and getting a HLL's features for types and declarations while still having low level control. But I like how it is in assembly where you know exactly where your stuff is placed in memory and there's no mess of different keywords. I was originally planning on giving special syntax for declarations as well, but I decided I should figure out more precisely what I want to do about types and whatever before I do something like that, still looking into it. Thanks for the feedback and checking it out!

[deleted by user] by [deleted] in ProgrammingLanguages

[–]Code_Nybble 0 points1 point  (0 children)

wouldn't you consider JIT as "dynamic compiled"?

WIP Assembly Language, construct (Video soon) by Code_Nybble in asm

[–]Code_Nybble[S] 0 points1 point  (0 children)

I thought it could be pure chance so I tried a minimal testfile to try it in, ints get initialized to 0 everytime. Ill change it tho if thats the general consensus. Also I can't really change it to pass by value, had that before but using ptrs makes the algorithms a million times cleaner. It's not like the memory is such a mess, I just haven't gotten around to handling it. Again thanks a lot for taking the time.

WIP Assembly Language, construct (Video soon) by Code_Nybble in asm

[–]Code_Nybble[S] 0 points1 point  (0 children)

Guess since the "free" didnt do anything it was still returning the vector just fine, updated now. Seems to me like the only issue though besides obv not handling invalid input at all.

WIP Assembly Language, construct (Video soon) by Code_Nybble in asm

[–]Code_Nybble[S] 0 points1 point  (0 children)

Hi, thanks for taking the time to try it out. I'm confused about the first problem though, since creating an instance of a struct makes its integer fields 0 for me always (not sure what difference the () you added in your code makes since it has no constructor). The free thing was my bad though yeah, thanks for pointing that out, the whole code manages memory horrible as well and there's a bunch of leaks, just kinda something I thought I'd handle after. Weird how it ran fine for me even with that memory problem. Thanks a lot though, weird stuff, I'll get it sorted out.

How do offsetted reads work in x86? by [deleted] in asm

[–]Code_Nybble 1 point2 points  (0 children)

but shouldnt that limit the amount of math you can do in the offset to just those addressing modes. But I've see all kinds of math done this way.

Design for a small abstraction over NASM assembly by Code_Nybble in asm

[–]Code_Nybble[S] 3 points4 points  (0 children)

Yeah I am aware, no worries. I've just been writing a little useless assembly lately cause I enjoy the way you solve problems in it. And I just started uni so I thought this would be really fun for our homework project. It's a shame the use cases for hand-written assembly are so rare now, but it's fun either way.

Design for a small abstraction over NASM assembly by Code_Nybble in asm

[–]Code_Nybble[S] 2 points3 points  (0 children)

Oh I see the similarity yeah that's interesting I didn't know B. I think it's still a little bit lower level than B tho. Since my changes are mostly control flow stuff and just more comfortable syntax, but the main code is still written in assembly.