Macros in C++

Поділитися
Вставка
  • Опубліковано 16 гру 2017
  • Patreon ► / thecherno
    Twitter ► / thecherno
    Instagram ► / thecherno
    Discord ► thecherno.com/discord
    Series Playlist ► thecherno.com/cpp
    Thank you to the following Patreon supporters:
    - Dominic Pace
    - Kevin Gregory Agwaze
    - Sébastien Bervoets
    - Tobias Humig
    - Peter Siegmund
    - Kerem Demirer
    Gear I use:
    -----------------
    BEST laptop for programming! ► geni.us/pakTES
    My FAVOURITE keyboard for programming! ► geni.us/zNhB
    FAVOURITE monitors for programming! ► geni.us/Ig6KBq
    MAIN Camera ► geni.us/t6xyDRO
    MAIN Lens ► geni.us/xGoDWT
    Second Camera ► geni.us/CYUQ
    Microphone ► geni.us/wqO6g7K

КОМЕНТАРІ • 266

  • @karmaindustrie
    @karmaindustrie 5 років тому +515

    #define print(x) std::cout

    • @IamusTheFox
      @IamusTheFox 5 років тому +63

      Or with type safty, and proper compile time checking:
      template
      constexpr void print(Tostream ostrem = std::cout, Tlimit end='
      ' ,TStr ... to_print)
      {
      (std:: cout

    • @kcvinu
      @kcvinu 4 роки тому +48

      #define begin {
      #define end } ;
      voilà ! pascal. And use just "end", voilà ! Ruby. :) cpp is really fun.

    • @ShadowaOsu
      @ShadowaOsu 4 роки тому +12

      @@IamusTheFox you defined a template Tostream and never used it lmao

    • @IamusTheFox
      @IamusTheFox 4 роки тому +4

      @@ShadowaOsu lmao, you're right, my bad.

    • @ShadowaOsu
      @ShadowaOsu 4 роки тому +7

      ​@@IamusTheFox also it gives compile error for various of inputs when used in main, so I tried to give it a try as well
      struct End {
      const char* end;
      constexpr End() : end("
      ") { }
      constexpr End(const char* end) : end(end) { }
      };
      template
      constexpr auto pyprint (const First& first, const Rest& ...rest) -> void {
      if constexpr (sizeof... (rest) > 0) {
      std::cout

  • @Banom7a
    @Banom7a 6 років тому +700

    #define true false

  • @DiamondShocked
    @DiamondShocked 4 роки тому +43

    I think it would also be helpful to show common pitfalls of parameterized macros, such as the following 2 examples:
    ===================
    #define MAX(x, y) x > y ? x : y
    int main() { return MAX(7,5) * 10; }
    Here main() will return 7 instead of 70:
    7 > 5 ? 7 : 5 * 10 ==> 7
    To fix this, do:
    #define MAX(x, y) (x > y ? x : y)
    ===================
    Another issue can be seen in this example:
    #define MULT(x, y) (x * y)
    int main() { return MULT(2+5, 10); }
    Here main() will return 52 instead of 70:
    2+5*10 ==> 52
    To fix this, do:
    #define MULT(x,y) ((x) * (y))
    Of course, y can be a pointer so it is possible that *(y) is seen as a dereference. In addition, either x or y can be almost any text which can result in weird generated code.
    ===================
    The takeaway is that parameterized macros are NOT functions: they simply replace symbols with parameterized text.
    This can also result in the problem of massive code duplication, since a parameterized macro does not define a function in the program text segment, but is rather copied to every invocation.

  • @nimrodhawk4011
    @nimrodhawk4011 3 роки тому +124

    The thought of seeing an “OPEN_CURLY” macro in real life cracked me up...at that point you know you’re dealing with a high-effort troll lmao

    • @sebastiangudino9377
      @sebastiangudino9377 2 роки тому +11

      I once saw a
      #define begin {
      #define end }
      And it was honestly a pretty wild experience. That simple change made C++ feel a hell of a lot like Ruby or Basic. Like:
      void main() begin
      if (1 > 0) begin
      printf("whatever
      ");
      end
      end
      Doesn't that look wild?

    • @failgun
      @failgun 2 роки тому +7

      @@sebastiangudino9377 reminds me of Lua too

    • @zltn_brkl
      @zltn_brkl 2 роки тому +4

      #define semicolan ;

    • @jstro-hobbytech
      @jstro-hobbytech Рік тому +20

      My wife was like "what are you laughing so hard at?". I told her she wouldn't understand. She made me explain. She didn't understand.

    • @phantomstriker7996
      @phantomstriker7996 Рік тому +4

      Saw one image where he just defined some stuff and the code was like "frfr no cap" and he just replaces so many things with just random words and it looks like a sentence.

  • @johnsmith-ci5ib
    @johnsmith-ci5ib 3 роки тому +56

    These have got to be the most concise and clear programming videos I've seen thus far.

  • @redcollard3586
    @redcollard3586 Рік тому

    Thanks for these videos man, I'm reading "Code Complete" and I thought I was getting to know C++ and C pretty well but everything he says about macros has gone over my head. This clears everything up, as so many of your videos do. The Static and Cost ones are my other favorites so far can't wait to see the rest this series is literally better than a college education.

  • @hallerinstruments318
    @hallerinstruments318 4 роки тому +30

    You're an excellent educator. Great job! This was super helpful.

  • @DanielLiljeberg
    @DanielLiljeberg 6 років тому +100

    As some might have noticed the "blank" macro would actually not remove the entire LOG line in the code. It would leave the ";". This might cause people to want to include the ";" in the macro instead of writing it after the macro in the source code since that would not leave a line with just a ";". But a line with only ";" is totally acceptable and is just an empty statement which a decent compiler would most likley simply discard although there might exist some compilers that would actually insert NOOP instructions.
    Point is, ";" by itself on a line is perfectly legal code.

    • @nathannlatimore7863
      @nathannlatimore7863 3 роки тому

      Thanks for the clarification! Really appreciate it!

    • @logangraham2956
      @logangraham2956 3 роки тому +1

      but you might want to be aware of this if it isn't by itself.

    • @robertmoats1890
      @robertmoats1890 2 роки тому +8

      Its sometimes better to define the empty output as "{}" or "((void)0)" - These will make it a valid line of code without it doing anything. This is important if your macro can be called from within a single condition line, like if(x) MACRO();

    • @Laevatei1nn
      @Laevatei1nn 2 роки тому

      called null statement

    • @kushalghosh5150
      @kushalghosh5150 Рік тому

      it is good to be aware of this but it doesn't matter if there is an extra colon ; after a statement

  • @zaviermiller8980
    @zaviermiller8980 2 роки тому

    Bruh I love that I can expect a good ass cherno video on any cop topic I might want to learn. Really appreciate the work man 🙌🙌🙌

  • @firerazzer
    @firerazzer 5 місяців тому +2

    Really usefull compiler option : -E
    It wills just process the precompiler routine and output your source code with all macro expanded.
    For example : g++ -E main.cpp -o main.e

  • @psposki
    @psposki 4 роки тому +6

    It's so comfy to watch it, I wish my lecturer was talking and makeing examples like you.

  • @likestomeasurestuff3554
    @likestomeasurestuff3554 6 років тому +2

    Thank for this series, helps a lot

  • @10monthspregnant
    @10monthspregnant 6 років тому +21

    Really loved the optimization of std::vector video. More videos on optimizing commonly libraries and functions would be super useful!

    • @alltheway99
      @alltheway99 4 роки тому

      Or STL container comparisons and algorithms 🙂

  • @maryambeygmohammadi2232
    @maryambeygmohammadi2232 2 роки тому +1

    good explained and helpful, thanks Cherno!

  • @syeduthman
    @syeduthman 5 років тому +35

    I use macros for Embedded microcontroller to configure my hardware easily.

  • @VasaMusic438
    @VasaMusic438 5 років тому

    your indications are very wise, thanks a lot !!

  • @kiritsuna
    @kiritsuna 4 роки тому

    This video really helped me understand a lesson of learncpp, thanks a lot

  • @neiltsakatsa
    @neiltsakatsa 6 років тому +26

    Streams, Input and Output. As well as Files

  • @PeterPetrakis
    @PeterPetrakis 6 років тому +2

    Your example of logging bytes would be better served by creating a custom allocator that handled the metrics. Then you would override new to use your allocate/create functions. The bonus here is that you could add that allocator to a container and reap the same benefits.

    • @TheCherno
      @TheCherno  6 років тому +1

      Yes, but you still might want to track the file and line the allocation came from, which would require a macro.

  • @kaydenstevens5193
    @kaydenstevens5193 5 років тому +6

    The advice at 3:20 is golden bro!

  • @billbez7465
    @billbez7465 4 роки тому

    Excellent C++ series. I am now a patreon.

  • @gwennigboudeau7512
    @gwennigboudeau7512 4 роки тому

    Very good video and clear explanation

  • @darealshinji
    @darealshinji 2 роки тому +3

    Other real life examples for macros would be to target different platforms. You write a conditional to decide between using Windows API or POSIX API. Or you want to do different stuff for an ARM build compared to x86. In open source projects macros are often used for optional features which might be enabled during configuration, like building ffmpeg with lots of optional third party libraries enabled. You can use macros to enable compiler specific stuff, like telling msvc right in the code to link against a library, but you want that part to be "excluded" for other compilers that don't understand or need this. Macros may also play a role when you build static libraries and DLLs for Windows, as the symbols in a header file need to be declared as either importing or exporting code or none of that.

  • @Mario112352
    @Mario112352 6 років тому +7

    Really like your C++ series.
    Wondering if you could do some videos on MVS Windows GUI.
    Not much out there on the Windows GUI, I know there are at least one error with MVS 17 in loading a Windows GUI setup. This is really tough for beginners.
    Thanks,

  • @Fronzel.Neekburm
    @Fronzel.Neekburm 2 роки тому +3

    Great series, these are presented really well. I don't understand why "#ifdef symbol" or "#ifndef symbol" is bad though. Header files have used this method to see if it has already been included for ages, windows header use it a lot and use it to set function names for Unicode or ascii. Would have been a good time to explain the underscore in symbol names. Still great simple video series worth watching.

  • @Danny-ck6iw
    @Danny-ck6iw 2 роки тому

    This is te best explanation for this that I have seen on this flawed website known as UA-cam, thank you

  • @koenderbb5191
    @koenderbb5191 4 роки тому +8

    Hi Cherno,
    I know you will touch / have touched upon macros in more depth in your game engine / opengl series, but could you still make a separate video that's purely about macros (a part 2 of this one)? Because I don't follow your game engine / opengl series but I would still like to learn more about it from you.
    Thanks ~

  • @sanskar_choudhary
    @sanskar_choudhary 3 роки тому

    Nice explaination 👍🏻

  • @OzieCargile
    @OzieCargile 3 роки тому

    You are an excellent teacher.

  • @ZER02641988
    @ZER02641988 6 років тому +4

    When we can expect the video in which you are going to show macros in more details and built in macro types , mentioned in this video?

  • @ogox
    @ogox 6 років тому +4

    Hey, great videos! Can you please make a video about the volatile keyword? :)

  • @AssemblyWizard
    @AssemblyWizard 6 років тому +9

    Another problem with the code is that LOG in release mode doesn't force a semicolon.

  • @ZzBiazZ
    @ZzBiazZ 6 років тому +1

    thank you

  • @logangraham2956
    @logangraham2956 3 роки тому +4

    actually the
    LOG(...);
    in release mode would become
    ;
    because the semicolon was not defined in the macro.

  • @scullyy
    @scullyy 3 місяці тому +1

    It no longer becomes simple copy paste when using any punctuation characters in the macro name. This code here for example, is not allowed:
    #define print(x) std::cout

  • @MegaNightdude
    @MegaNightdude 3 роки тому

    Awesome!

  • @RoshanPradhan2
    @RoshanPradhan2 3 роки тому +29

    Let's make Python with #define 😂

  • @strawberriecherrie
    @strawberriecherrie 3 роки тому +1

    I am learning SOOOO much more than what i did i uni!

  • @djupstaten2328
    @djupstaten2328 Рік тому +1

    Thank you for these incredible videos. I noticed in VS Code, some C++ I had installed offered a -- *lightbulb* | "inline macro?" | -- clickable tooltip that will let you graphically resolve whatever macro you are currently hovering over. Surely there are tools in actual Visual Studio to do that globally? Or stepwise for safety.

  • @bluescanfly1981
    @bluescanfly1981 2 роки тому

    Macros are useful for writing parametrized test cases or "procedurally generated" code in general.
    Clojure / Lisp take it to the next level with homoiconicity (code and data are the same thing)

  • @robertmoats1890
    @robertmoats1890 2 роки тому +2

    In some cases, you may want to define your empty macro (the release version) as "{}" or "((void)0)", such as..
    #define MACRO(x) ((void)0)
    This will result in the macro generating a valid line of code that doesn't actually do anything. This would be important, if for example, you wanted to use it in places such as..
    if( xyz )
    MACRO(x);
    I usually define a special "#define EMPTY_STATEMENT ((void)0)" somewhere near the top of my code to be used in these cases. It makes the macros themselves a little more readable ( #define MACRO(x) EMPTY_STATEMENT )

  • @chainonsmanquants1630
    @chainonsmanquants1630 3 роки тому

    Thanks

  • @behrampatel3563
    @behrampatel3563 2 роки тому

    You would have made an excellent Unreal Engine C++ trainer. Please do consider making a course on UE C++

  • @marcinlesniewski4571
    @marcinlesniewski4571 3 роки тому

    Elegancko

  • @RootsterAnon
    @RootsterAnon 3 роки тому +3

    if Anyone is watching this in 2020. If your Debug Code is not recognized after checking for PR_DEBUG you just need _DEBUG now. Hope this helps.

  • @LoneDWispOfficial
    @LoneDWispOfficial 2 роки тому +2

    video idea for anyone just for fun: Making c++ looks like another programming language, using only MACROS!

  • @rcookie5128
    @rcookie5128 6 років тому

    yay!

  • @mattgraves3709
    @mattgraves3709 3 роки тому

    Awesome.

  • @10monthspregnant
    @10monthspregnant 6 років тому +1

    With the knowledge we have now, does anyone have any recommendations for medium sized C++ projects? Maybe making use of OpenCV?

  • @nickmichael7206
    @nickmichael7206 6 років тому

    Would using the # define WAIT std::cin.get() still be bad for debugging purposes? If I am not using vim or some text editor that doesn't have break points, that looks like a pretty quick way to use my own sort of break point, especially if I am going to delete it after I am done writing the code anyway.

  • @zdenkobrazda4041
    @zdenkobrazda4041 4 роки тому

    ILOVETHIS

  • @jadespy399
    @jadespy399 2 роки тому

    Another reason why it might not be the best -- although IMO it's silly -- is that someone might tack a

  •  6 років тому

    very good. can you train qt. so we can make mobile application without lost of change of our code. Qt has opengl, opengl-es(angle) and vulkan implementations

  • @henrikschou3789
    @henrikschou3789 6 років тому

    Many a video about APIs I here about them all the time. I wood like to know: Wot they are and how they works?

  • @Rakesh-yu1pb
    @Rakesh-yu1pb 4 роки тому +2

    what an intelligent human being.

  • @CheckmateStallioN
    @CheckmateStallioN 4 роки тому

    Wouldn't it be usually better to use inline functions instead? They are safer and the performance difference is negligible. I know function calls use more cpu cycles but from my understanding inline functions are very optimized. I remember this from Effective C++ book

  • @YXalr
    @YXalr 6 років тому +3

    Wouldn't
    #define LOG(x)
    leave an extra semicolon in the code as it is not part of the definition?

    • @rcookie5128
      @rcookie5128 6 років тому +5

      yes it would in his example, but just a semicolon without any statements doesn't do anything

  • @hsmhsm327
    @hsmhsm327 2 роки тому

    Java: *public static void main* is untouchable if you want your code to compile.
    c++: hold my *MAIN_MARCO CHAR_EXCLAMATION*

  • @haos4574
    @haos4574 6 років тому

    Function pointers needed

  • @senatorpoopypants7182
    @senatorpoopypants7182 3 роки тому +1

    why is this so funny to me. I need to grow up and get my big boy coder pants.

  • @jannesopanen8032
    @jannesopanen8032 3 роки тому

    Good tutorial but if you use #define LOG(x), without anything, it compiles and works fine but the error code i get is weird? not 0 or 1.

  • @mba2ceo
    @mba2ceo Рік тому +1

    is there a way to refer an array element by a name ? ex: #define a1 a[1]; a1=1; ?

  • @coolkoala282
    @coolkoala282 4 роки тому +2

    Both Programming and English can be learned by watching your videos

  • @astaghfirullahalzimastaghf3648
    @astaghfirullahalzimastaghf3648 3 роки тому

    @3:02
    Damn,
    That was useful
    Because I don't like to type
    "std::cout

  • @muhamadabdulsamad2815
    @muhamadabdulsamad2815 6 років тому +7

    Hey Cherno, thanks for your wonderful lectures they're really awesome and they helped me a lot! But the only tiny problem is in your lessons when you going through the lessons you speak and explain so fast lol so I'm asking if you just could be a bit slower for sharing knowledge about c++ I'll be grateful
    Thanks for everything ~ 😁

    • @b0606089
      @b0606089 4 роки тому +4

      Reduce the playback speed to 0.75x.

  • @ccpmustfall6445
    @ccpmustfall6445 3 роки тому

    For people having issues for ifdef DEBUG not showing correctly.
    Use #Ifdef _DEBUG
    I think the visual studio 2019 changed something for the debug :)

  • @Daninshit
    @Daninshit 3 роки тому

    Define macros are easy, the difficult is to read, most of the time you don't know where they are and what they do. Some code depend of some macros to be defined and the docs sometimes don't put so much effort in explain it, and that's really confusing.

  • @shipweck6253
    @shipweck6253 11 місяців тому

    3:33 OOP programmers: nah im gonna make everything OOP

  • @bloodwolf8307
    @bloodwolf8307 4 роки тому

    cool

  • @sida_g567
    @sida_g567 3 роки тому

    Wow

  • @abhijeetjain04
    @abhijeetjain04 5 років тому

    #DontstopOPENGLseries , lot of things are still to be covered in there !!!

  • @kenan2386
    @kenan2386 2 роки тому +2

    /* use this at your own risk */
    #define true false
    #define int
    #define if while
    #define else
    we do a large amount of trolling

  • @relytheone853
    @relytheone853 8 місяців тому

    Where should I move on after finishing these series?

  • @DainYanuka
    @DainYanuka 5 років тому

    Does usage of macros effect performance or increase time in compilation since it needs to replace texts, like specially if the program has large number of macros?

    • @angelcaru
      @angelcaru 3 роки тому

      If you have a large number of macros, you should probably reconsider your code.

    • @BukanChurchill
      @BukanChurchill 2 роки тому +1

      @@angelcaru or your programming career

  • @TheDa6781
    @TheDa6781 3 роки тому

    OMG thank you.This is exactly what i was looking for. OPEN_CURLY it is. No.. WAIT

  • @Cyraxx13
    @Cyraxx13 6 років тому +86

    Please don't pull another "Cherno" on us. Like you hype us with your quality content and then suddenly dissapear for half a year... :(

  • @Symphonixz
    @Symphonixz 2 роки тому

    this is cool and all, but wouldn't this require wrapping a good portion of code with "LOG(x)" or are you just using Macros for short code to become shorter? Excuse me for being dumb here, but could you give me another example where you could use Macros to do "stuff" as it is currently shown to put shorter code instead of typing the larger amount. I do find it interesting where you showed in "Release Mode" some code can be used or not used.

  • @kvanctok9234
    @kvanctok9234 3 роки тому

    The Cherno: C++
    Subtitles/CC: *zip ocelots*

  • @user-bk8rp9zj6q
    @user-bk8rp9zj6q Рік тому

    Slack in Unreal Engine uses macroses extensively and code becomes so cryptic...

  • @bunty9560
    @bunty9560 4 роки тому

    @Cherno What Should I start first, 'Game Engine' playlist or 'OpenGL' ?

    • @koenderbb5191
      @koenderbb5191 4 роки тому +1

      I haven't seen either, but I guess it would make more sense to start with OpenGL

  • @Ali2010247
    @Ali2010247 6 років тому +2

    Typedefs?

  • @kcvinu
    @kcvinu 4 роки тому

    You are really great. I started learning cpp in 2013 but quit learning only because of curly brackets and over use of symbols like "

    • @piechulla1966
      @piechulla1966 4 роки тому

      This joke has probably been cracked over 100000 times since Kernighan & Ritchie presented C in 1971.

  • @slaincow4032
    @slaincow4032 6 років тому

    *missed a lot of episodes* time to bing 😂

    • @slaincow4032
      @slaincow4032 6 років тому +1

      *Calculates minutes in all episodes combined* 10 HOURS?

  • @relytheone853
    @relytheone853 8 місяців тому

    Can I set debug mode in Linux using vscode?

  • @YamamotoGenryusaiShigekuni
    @YamamotoGenryusaiShigekuni Рік тому +1

    I have a question. Can we redefine a preprocessor directive? For instance (#define ADD_LIB #include)

    • @MaxCE
      @MaxCE 9 місяців тому

      it doesn't work for normall defines

    • @MaxCE
      @MaxCE 9 місяців тому

      as for macros it doesn't work because # has a special meaning in macros

  • @aaamos16
    @aaamos16 Рік тому +1

    Why can't you put template functions in.cpp files

  • @dognip
    @dognip 4 роки тому +1

    3:50 you're welcome

  • @kinglijah9723
    @kinglijah9723 5 років тому

    On that first code you wrote, there wasn't a "return 0;"
    so when do I use the Return 0;

    • @IamusTheFox
      @IamusTheFox 5 років тому

      @Peterolen You can even go crazy and have `void main();` Not that you should, ever. Seriously, don't.

    • @darealshinji
      @darealshinji 2 роки тому

      I don't like that he keeps omitting the return statement in main. I guess msvc silently optimizes it to return 0 or something like that. GCC will usually warn you and using "void main()" might not even be possible.

  • @rogerbreton6412
    @rogerbreton6412 4 роки тому

    Do you do any consulting?

  • @eotcoldhymns2930
    @eotcoldhymns2930 4 роки тому

    What IDE are you using or do you recommend for C/C++ development on linux?

    • @xrafter
      @xrafter 4 роки тому

      @Artem Katerynych
      Clion is available in linux

    • @chiragsingla.
      @chiragsingla. 2 роки тому

      I don't use ide I use visual studio code with c++ extension and cmake extensions

  • @MichaelYoussry
    @MichaelYoussry 6 років тому +3

    How is that different from inlined functions?

    • @TheCherno
      @TheCherno  6 років тому +8

      Macros have nothing to do with functions, they're just text that is replaced. You could use them like a function, however you can do so much more with them. We'll explore this in later episodes.

    • @TheCherno
      @TheCherno  6 років тому +1

      Functions will get inlined if you use the appropriate keyword (eg. __force_inline for MSVC).

    • @somedude4122
      @somedude4122 6 років тому

      @TheChernoProject The code it will create tends to be the same though.

    • @courier7049
      @courier7049 6 років тому +2

      The fact that an "inline" function is inlined is decided by compiler, macros do not care about type safety or code syntax as they are parsed at preprocessing phase and are simple "find/replace" expressions. The most fun is to debug a macro because if for an inline function debugger will jump into function in case of a macro there is no code to jump to as the name of the macro was already replaced with specific text.

    • @somedude4122
      @somedude4122 6 років тому

      Well, yes, but macros are really useful where such text replacement is needed.

  • @RealityCheck6969
    @RealityCheck6969 8 місяців тому

    They should have used an assignment operator. People would understand instantly.

  • @user-rr8hc8ls5n
    @user-rr8hc8ls5n 2 роки тому

    So you can create lua with macros, end is }, and so on

  • @milan_shah
    @milan_shah 3 роки тому

    This video was quite helpful.
    Could you please make a similar video but using VSCode? Thank you in advance!

  • @higuy55100
    @higuy55100 6 років тому +1

    2:24 Double negative : "nothing you can't not replace" = "nothing you can replace"

  • @huyvole9724
    @huyvole9724 6 років тому +1

    Now I realize Properties >> C/C++ >> Preprocess Def is macro.
    I remember when I used static/dynamic library, I into Properties >> Linker blah blah ... hahahahahah Now I confident to use macro #pragma comment(lib, "nameLib.lib")

  • @19n05k83
    @19n05k83 4 роки тому

    Nordic nRF SDK for their microcontrollers is completely written in macros (C not C++). It's a nightmare.

    • @darealshinji
      @darealshinji 2 роки тому

      I've once seen a tiny single header file PNG decoder which was written almost entirely using macros. It was... interesting.

  • @MaxCoplan
    @MaxCoplan 4 роки тому +1

    Why does he build for x86 and win32?

    • @piechulla1966
      @piechulla1966 4 роки тому

      Google WOW64 or watch all TheCherno clips. Imagine a customer who still wants to run your application on 32 bit windows. Imagine the effort to maintain two versions of your application. You understand?

  • @marshall02019
    @marshall02019 5 років тому

    i like the video but hate the grandma couch

  • @jannesopanen8032
    @jannesopanen8032 3 роки тому

    Never mind, apparently I broke my ten beer limit, so this one is on me.