March 6, 2024: Dwarf Fortress 50.12 has been released.
News: February 3, 2024: The February '24 Report is up.
News: February 4, 2021: Dwarf Fortress Talk #28 has been posted.
News: November 21, 2018: A new Threetoe story has been posted.
Forum Guidelines
(Ok, granted, it lacks a preprocessor and it's not extensible, but then again, most languages aren't)You can always use cpp for macros and whatever.
[ron@Tux:~]$ cat hello.cs
#define TEXT "hello, world!"
class Hello {
static void Main() {
System.Console.WriteLine(TEXT);
}
}
[ron@Tux:~]$ cpp hello.cs | awk "NR>5" > temp.cs
[ron@Tux:~]$ dmcs temp.cs && rm temp.cs
[ron@Tux:~]$ mono ./temp.exe
hello, world!
cpp can be used anywhere, it doesn't look very good, but it's all a matter of adding another line to your Makefile.(Ok, granted, it lacks a preprocessor and it's not extensible, but then again, most languages aren't)You can always use cpp for macros and whatever.
[ron@Tux:~]$ cat hello.cs
#define TEXT "hello, world!"
class Hello {
static void Main() {
System.Console.WriteLine(TEXT);
}
}
[ron@Tux:~]$ cpp hello.cs | awk "NR>5" > temp.cs
[ron@Tux:~]$ dmcs temp.cs && rm temp.cs
[ron@Tux:~]$ mono ./temp.exe
hello, world!
Linux runs on pac-man... and yogurt?They say on runs on kerosene-powered cheese graters too
What does it say when you try to access the memory directly?So you're saying the only way to prevent this "padding," is to write the members one by one?
C might be "padding" your values in your struct, they're not guaranteed to be consecutive. Especially since you use multiple types in one struct.
void write_bitmap (canvas c, FILE *f)
{
BITMAPINFOHEADER h = mkheader(c);
fwrite(&h, sizeof(BITMAPINFOHEADER), 1, f);
}
...
$ hexdump -cV file
00000000 42 4d 00 00 66 00 00 00 00 00 00 00 36 00 00 00 |BM..f.......6...|
00000010 28 00 00 00 04 00 00 00 04 00 00 00 01 00 18 00 |(...............|
00000020 00 00 00 00 30 00 00 00 00 02 00 00 00 02 00 00 |....0...........|
00000030 00 00 00 00 00 00 00 00 |........|
00000038
Those two 00s after 42 4d aren't supposed to be there, and when writing individual parts of the struct, they aren't:void write_bitmap (canvas c, FILE *f)
{
BITMAPINFOHEADER h = mkheader(c);
fwrite(&h.magic, sizeof(uint16_t), 1, f);
fwrite(&h.size, sizeof(uint32_t), 1, f);
}
...
$ hexdump -vC file
00000000 42 4d 66 00 00 00 |BMf...|
00000006
For both openoffice is more than ok. I really doubt there would be a difference with word.Umm.. No, not really. Have you even tried Word? It's far more stable, it's faster, it doesn't crash, it doesn't flip your text all over the place, it parses doc/docx correctly, and it does right-to-left paragraphs correctly. I can go on, but I think you get the picture.
I mean ok, word have a few cool features but there isn't such a difference between the two, especially for simple task like that.