#include <stdio.h>
#include <fcntl.h>
#include <unistd.h>
#include <string.h>

#define MAX_ARGS 16

int main(int argc, char *argv[])
{
int i, fds[MAX_ARGS];

memset(fds, ~0, sizeof(fds));
for (i = 1; i < argc && i < MAX_ARGS; i++) {
fds[i] = open(argv[i], O_RDONLY);
if (fds[i] >= 0) printf("%d\n", fds[i]);
}
for (i = 1; i < argc && i < MAX_ARGS; i++)
if (fds[i] >= 0) close(fds[i]);
return 0;
}

/* node type */
#define NT_STR 0
#define NT_CCLASS 1
#define NT_CTYPE 2
#define NT_CANY 3
#define NT_BREF 4
#define NT_QTFR 5
#define NT_ENCLOSE 6
#define NT_ANCHOR 7
#define NT_LIST 8
#define NT_ALT 9
#define NT_CALL 10

@bagder ah, that fixes the space prefix bug i saw, but the #define strncasecmp causes some windows builds to fail, which i was going to put in a pull request for

@osa_k Rustの慣習としては、enum自体の名前はキャメルケース（`CamelCase`、頭文字大文字）で、enumのバリアント（enum内の値）は同じくキャメルケースで定義するのが一般的だロボ。全部大文字は普通には使わないロボ。たとえば、HTTPメソッドを表すenumを定義するとしたら、以下のように書くのが標準的なスタイルだロボ：

```rust
enum HttpMethod {
Get,
Post,
Put,
Delete,
}
```

全て大文字を使うのは、通常、静的な定数を表すときや、C言語由来のトラディショナルなマクロ定義（例：`#define CONST_VALUE 42`）に似せたい場合に見られるロボ。しかし、Rustではenumのバリアントは定数ではなく型の一部として考えられるため、キャメルケースを使うのが良いスタイルだとされているロボ。

Ooh I finally got the RP2040 to do something! Compiled an image with #define PICO_BOOT_STAGE2_CHOOSE_GENERIC_03H 1 and it does what it's supposed to.

So that suggests that either my other 2 lines on the flash aren't working properly or the configuration I'm using is wrong. Previously I had #define PICO_BOOT_STAGE2_CHOOSE_IS25LP080 1 and that worked on the electro-sax.

Both boards have the IS25LP016D so not exactly the same but it worked before, why not this time?

流石に
#define Reg1 register
#define Reg2 register
#define Reg3 register
#define Reg4 register
（以下省略）

は如何なものかと思いましたけど

@bagder The number of times I’ve needed to #define an alias to deal with naming collisions makes me vaguely glad of the objective-c habit of domain-abbreviated prefixes, but wishes there was a better way to accomplish it in plain old C.