I foreningen Bitraf (orgnr. 898124452), Torsdag 19. oktober 2017, Pløensgate 4, Oslo
Dette er et uformelt møte for medlemmene i foreningen, som supplement til den årlige generalforsamlingen.
| #!/usr/bin/env python | |
| #encoding: utf-8 | |
| # Copyright (C) 2013 @XiErCh | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining a copy | |
| # of this software and associated documentation files (the "Software"), to deal | |
| # in the Software without restriction, including without limitation the rights | |
| # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| # copies of the Software, and to permit persons to whom the Software is |
I foreningen Bitraf (orgnr. 898124452), Torsdag 19. oktober 2017, Pløensgate 4, Oslo
Dette er et uformelt møte for medlemmene i foreningen, som supplement til den årlige generalforsamlingen.
TCL-Expect scripts are an amazingly easy way to script out laborious tasks in the shell when you need to be interactive with the console. Think of them as a "macro" or way to programmaticly step through a process you would run by hand. They are similar to shell scripts but utilize the .tcl extension and a different #! call.
The first step, similar to writing a bash script, is to tell the script what it's executing under. For expect we use the following:
#!/usr/bin/expect
9 March, 2019
We were discussing with @erusev what we can do with async operation when using useReducer() in our application. Our app is simple and we don't want to use a state management library. All our requirements are satisfied with using one root useReducer(). The problem we are facing and don't know how to solve is async operations.
In a discussion with Dan Abramov he recommends Solution 3 but points out that things are fresh with hooks and there could be better ways of handling the problem.