I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.

I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?

I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.

The code is at
https://github.com/MalcolmMcLean/babyxrc

sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
>
> I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
>
> I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
>
> The code is at
> https://github.com/MalcolmMcLean/babyxrc

give some examples of how it work or something...
usenet is for discussint the matter things (at least in core)..

also imo people shoudl genrally asume that usenet is not
for opening links so people shouldnt post links to much imo
but if they post about something paste it as a text content

sobota, 5 sierpnia 2023 o 12:20:47 UTC+2 fir napisał(a):
> sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> >
> > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> >
> > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
> >
> > The code is at
> > https://github.com/MalcolmMcLean/babyxrc
> give some examples of how it work or something...
> usenet is for discussint the matter things (at least in core)..
>
> also imo people shoudl genrally asume that usenet is not
> for opening links so people shouldnt post links to much imo
> but if they post about something paste it as a text content

overally even opening the link and reading it for 3 minutes i got no idea what it is and what it does

its liek reading text in such kind of english that need to
know many things (assumptions) that are not provided..

it remembers me old times as when learning some things in
programing at start many things looks like that (many text
based on unknown information)... long time i hadnt such kind of
experiences... and overally i preffer the style that introduces things
not this one that dont introduces

On Saturday, 5 August 2023 at 11:20:47 UTC+1, fir wrote:
> sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> >
> > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> >
> > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
> >
> > The code is at
> > https://github.com/MalcolmMcLean/babyxrc
> give some examples of how it work or something...
> usenet is for discussint the matter things (at least in core)..
>
> also imo people shoudl genrally asume that usenet is not
> for opening links so people shouldnt post links to much imo
> but if they post about something paste it as a text content
>
It's a resource compiler. So it has a similar function to the resource compilers
included in Visual Studio or XCode. However instead of packaging the resources
into an opaque binary blob which can only be read by that platform, it
produces portable ANSI C output files which can be read anywhere.

So you write a little script file. If you want to include an image, it reads it and
spits out a 32 bit rgba buffer. If you want an audio clip, it spits out a list
of pcm values as shorts. If you want a string, it escapes it for you and spits out
a C string.

However its strength is that it also allows for a bit of processing of data.. So
images can be resized, or audio can be re-sampled to match the rate you want
in your program. Text can be taken in in one fomart and output in another, so
you can read ina UTF-8 file and have a UTF-16 string output. There's also a
brand new and experimental dataframe tag which loads a CSV file and produces
an array of C structs.

Here's a script file

<BabyXRC>
<string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
</BabyXRC>

Invoke the program like this

babyxrc hellobabyx.xml

Here's the output

char *hellobabyx = "Hello \"Baby X\"";

On Saturday, 5 August 2023 at 11:28:49 UTC+1, fir wrote:
> sobota, 5 sierpnia 2023 o 12:20:47 UTC+2 fir napisał(a):
> > sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > > I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> > >
> > > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> > >
> > > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
> > >
> > > The code is at
> > > https://github.com/MalcolmMcLean/babyxrc
> > give some examples of how it work or something...
> > usenet is for discussint the matter things (at least in core)..
> >
> > also imo people shoudl genrally asume that usenet is not
> > for opening links so people shouldnt post links to much imo
> > but if they post about something paste it as a text content
> overally even opening the link and reading it for 3 minutes i got no idea what it is and what it does
>
> its liek reading text in such kind of english that need to
> know many things (assumptions) that are not provided..
>
> it remembers me old times as when learning some things in
> programing at start many things looks like that (many text
> based on unknown information)... long time i hadnt such kind of
> experiences... and overally i preffer the style that introduces things
> not this one that dont introduces
>
That's valuable information. The documentation might need improving.

sobota, 5 sierpnia 2023 o 12:41:11 UTC+2 Malcolm McLean napisał(a):
> On Saturday, 5 August 2023 at 11:20:47 UTC+1, fir wrote:
> > sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > > I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> > >
> > > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> > >
> > > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
> > >
> > > The code is at
> > > https://github.com/MalcolmMcLean/babyxrc
> > give some examples of how it work or something...
> > usenet is for discussint the matter things (at least in core)..
> >
> > also imo people shoudl genrally asume that usenet is not
> > for opening links so people shouldnt post links to much imo
> > but if they post about something paste it as a text content
> >
> It's a resource compiler. So it has a similar function to the resource compilers
> included in Visual Studio or XCode. However instead of packaging the resources
> into an opaque binary blob which can only be read by that platform, it
> produces portable ANSI C output files which can be read anywhere.
>
> So you write a little script file. If you want to include an image, it reads it and
> spits out a 32 bit rgba buffer. If you want an audio clip, it spits out a list
> of pcm values as shorts. If you want a string, it escapes it for you and spits out
> a C string.
>
> However its strength is that it also allows for a bit of processing of data. So
> images can be resized, or audio can be re-sampled to match the rate you want
> in your program. Text can be taken in in one fomart and output in another, so
> you can read ina UTF-8 file and have a UTF-16 string output. There's also a
> brand new and experimental dataframe tag which loads a CSV file and produces
> an array of C structs.
>
> Here's a script file
>
> <BabyXRC>
> <string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
> </BabyXRC>
>
> Invoke the program like this
>
> babyxrc hellobabyx.xml
>
> Here's the output
>
> char *hellobabyx = "Hello \"Baby X\"";

and what it do with images? or things like fonts?? make char* array with initialiser or what?

sobota, 5 sierpnia 2023 o 12:41:11 UTC+2 Malcolm McLean napisał(a):
> On Saturday, 5 August 2023 at 11:20:47 UTC+1, fir wrote:
> > sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > > I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> > >
> > > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> > >
> > > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
> > >
> > > The code is at
> > > https://github.com/MalcolmMcLean/babyxrc
> > give some examples of how it work or something...
> > usenet is for discussint the matter things (at least in core)..
> >
> > also imo people shoudl genrally asume that usenet is not
> > for opening links so people shouldnt post links to much imo
> > but if they post about something paste it as a text content
> >
> It's a resource compiler. So it has a similar function to the resource compilers
> included in Visual Studio or XCode. However instead of packaging the resources
> into an opaque binary blob which can only be read by that platform, it
> produces portable ANSI C output files which can be read anywhere.
>
> So you write a little script file. If you want to include an image, it reads it and
> spits out a 32 bit rgba buffer. If you want an audio clip, it spits out a list
> of pcm values as shorts. If you want a string, it escapes it for you and spits out
> a C string.
>
> However its strength is that it also allows for a bit of processing of data. So
> images can be resized, or audio can be re-sampled to match the rate you want
> in your program. Text can be taken in in one fomart and output in another, so
> you can read ina UTF-8 file and have a UTF-16 string output. There's also a
> brand new and experimental dataframe tag which loads a CSV file and produces
> an array of C structs.
>
> Here's a script file
>
> <BabyXRC>
> <string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
> </BabyXRC>
>
> Invoke the program like this
>
> babyxrc hellobabyx.xml
>
> Here's the output
>
> char *hellobabyx = "Hello \"Baby X\"";

xml is terrible format imo, i would do nothing with xml..
why not json instead? not saying i like all that kind of files in
a world for some reason i managed to not use them all
but maybe its becouse i dont do related things

programing world today is full of trash and better not produce it more
but berret remove the trash from world..and removing trash is imo stainy with core narrow simplicity

On Saturday, 5 August 2023 at 11:46:46 UTC+1, fir wrote:
> sobota, 5 sierpnia 2023 o 12:41:11 UTC+2 Malcolm McLean napisał(a):
> > On Saturday, 5 August 2023 at 11:20:47 UTC+1, fir wrote:
> > > sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > > > I've been working on the Baby X resource compiler for some time now.. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> > > >
> > > > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> > > >
> > > > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
> > > >
> > > > The code is at
> > > > https://github.com/MalcolmMcLean/babyxrc
> > > give some examples of how it work or something...
> > > usenet is for discussint the matter things (at least in core)..
> > >
> > > also imo people shoudl genrally asume that usenet is not
> > > for opening links so people shouldnt post links to much imo
> > > but if they post about something paste it as a text content
> > >
> > It's a resource compiler. So it has a similar function to the resource compilers
> > included in Visual Studio or XCode. However instead of packaging the resources
> > into an opaque binary blob which can only be read by that platform, it
> > produces portable ANSI C output files which can be read anywhere.
> >
> > So you write a little script file. If you want to include an image, it reads it and
> > spits out a 32 bit rgba buffer. If you want an audio clip, it spits out a list
> > of pcm values as shorts. If you want a string, it escapes it for you and spits out
> > a C string.
> >
> > However its strength is that it also allows for a bit of processing of data. So
> > images can be resized, or audio can be re-sampled to match the rate you want
> > in your program. Text can be taken in in one fomart and output in another, so
> > you can read ina UTF-8 file and have a UTF-16 string output. There's also a
> > brand new and experimental dataframe tag which loads a CSV file and produces
> > an array of C structs.
> >
> > Here's a script file
> >
> > <BabyXRC>
> > <string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
> > </BabyXRC>
> >
> > Invoke the program like this
> >
> > babyxrc hellobabyx.xml
> >
> > Here's the output
> >
> > char *hellobabyx = "Hello \"Baby X\"";
> and what it do with images? or things like fonts?? make char* array with initialiser or what?
>
<BabyXRC>
<image src = "testimage.jpeg"></image>
<image name = "resizedimage" src = "image2.png" width = "256" height = "256"></image>
</BabyXRC>

This one is converting two images to C source.
The first is a jpeg. It loads it, the saves the data as a C array representing 32 bit rgba values.
The second is a png. However we want to give it a different name andd we want to resize it
to 256 x 256.

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> I've been working on the Baby X resource compiler for some time now.
....
> I don't have a Linux machine. If someone would be kind enough to
> valgrind it to check for memory leaks or worse bugs, that would be a
> help.

The README has no build instructions. I'm happy to guess, but other
users might not be.

--
Ben.

On Saturday, 5 August 2023 at 12:17:46 UTC+1, Ben Bacarisse wrote:
> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>
> > I've been working on the Baby X resource compiler for some time now.
> ...
> > I don't have a Linux machine. If someone would be kind enough to
> > valgrind it to check for memory leaks or worse bugs, that would be a
> > help.
> The README has no build instructions. I'm happy to guess, but other
> users might not be.
>
Thanks.
Yes, one problem is that when you are both the developer and doumenter,
you're so close to the project that it's eay to miss the obvious.

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> Here's a script file
>
> <BabyXRC>
> <string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
> </BabyXRC>

I'm struggling to find the cases where XML is either clearer or easier
than the resulting C, but then you know your users better than I do.

> Invoke the program like this
>
> babyxrc hellobabyx.xml
>
> Here's the output
>
> char *hellobabyx = "Hello \"Baby X\"";

Why not either

const char *hellobabyx = "Hello \"Baby X\"";
char hellobabyx[] = "Hello \"Baby X\"";

? You choice looks, at first lance, like the worst of the three.

--
Ben.

On Saturday, 5 August 2023 at 12:29:15 UTC+1, Ben Bacarisse wrote:
> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>
> > Here's a script file
> >
> > <BabyXRC>
> > <string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
> > </BabyXRC>
> I'm struggling to find the cases where XML is either clearer or easier
> than the resulting C, but then you know your users better than I do.
>
Try
<string name = "mynovel" src = "novel.txt"></string>

And you will see the advantage.over trying to enter a C string by hand.
>
> > Invoke the program like this
> >
> > babyxrc hellobabyx.xml
> >
> > Here's the output
> >
> > char *hellobabyx = "Hello \"Baby X\"";
> Why not either
>
> const char *hellobabyx = "Hello \"Baby X\"";
> char hellobabyx[] = "Hello \"Baby X\"";
>
> ? You choice looks, at first lance, like the worst of the three.
>
Fair point. I want to keep the output as simple as possible and I don't
make image buffers const. But maybe strings should be different.

sobota, 5 sierpnia 2023 o 12:57:25 UTC+2 Malcolm McLean napisał(a):
> On Saturday, 5 August 2023 at 11:46:46 UTC+1, fir wrote:
> > sobota, 5 sierpnia 2023 o 12:41:11 UTC+2 Malcolm McLean napisał(a):
> > > On Saturday, 5 August 2023 at 11:20:47 UTC+1, fir wrote:
> > > > sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > > > > I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> > > > >
> > > > > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> > > > >
> > > > > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
> > > > >
> > > > > The code is at
> > > > > https://github.com/MalcolmMcLean/babyxrc
> > > > give some examples of how it work or something...
> > > > usenet is for discussint the matter things (at least in core)..
> > > >
> > > > also imo people shoudl genrally asume that usenet is not
> > > > for opening links so people shouldnt post links to much imo
> > > > but if they post about something paste it as a text content
> > > >
> > > It's a resource compiler. So it has a similar function to the resource compilers
> > > included in Visual Studio or XCode. However instead of packaging the resources
> > > into an opaque binary blob which can only be read by that platform, it
> > > produces portable ANSI C output files which can be read anywhere.
> > >
> > > So you write a little script file. If you want to include an image, it reads it and
> > > spits out a 32 bit rgba buffer. If you want an audio clip, it spits out a list
> > > of pcm values as shorts. If you want a string, it escapes it for you and spits out
> > > a C string.
> > >
> > > However its strength is that it also allows for a bit of processing of data. So
> > > images can be resized, or audio can be re-sampled to match the rate you want
> > > in your program. Text can be taken in in one fomart and output in another, so
> > > you can read ina UTF-8 file and have a UTF-16 string output. There's also a
> > > brand new and experimental dataframe tag which loads a CSV file and produces
> > > an array of C structs.
> > >
> > > Here's a script file
> > >
> > > <BabyXRC>
> > > <string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
> > > </BabyXRC>
> > >
> > > Invoke the program like this
> > >
> > > babyxrc hellobabyx.xml
> > >
> > > Here's the output
> > >
> > > char *hellobabyx = "Hello \"Baby X\"";
> > and what it do with images? or things like fonts?? make char* array with initialiser or what?
> >
> <BabyXRC>
> <image src = "testimage.jpeg"></image>
> <image name = "resizedimage" src = "image2.png" width = "256" height = "256"></image>
> </BabyXRC>
>
> This one is converting two images to C source.
> The first is a jpeg. It loads it, the saves the data as a C array representing 32 bit rgba values.
> The second is a png. However we want to give it a different name andd we want to resize it
> to 256 x 256.

overally there is a question how usage of this resources as a /data section in exe is good... in green fire for example i used bitmap fonts nad put it into it then after all i found this bad and began to use a code which uses ttf fonts but 'stamped' in internal bitmap..no chance to beat the work of fontmakers imo those the people who made unparalelable work imo

overaly systems and their filesystems are weird this times imo they lack of order and restriction..overally it alweys makes me weird why those sytems ale o liberal and chaotic though not to say for some reasons this is better than my own style of doing things becouse if i would be dong thing it all would be more simple and probably restricted which im not sure is good - becouse my thinking tend to be rectangular, i think i would never invent such style as c has which more resembles me style of a plant, or something liek that

sobota, 5 sierpnia 2023 o 14:28:58 UTC+2 fir napisał(a):
> sobota, 5 sierpnia 2023 o 12:57:25 UTC+2 Malcolm McLean napisał(a):
> > On Saturday, 5 August 2023 at 11:46:46 UTC+1, fir wrote:
> > > sobota, 5 sierpnia 2023 o 12:41:11 UTC+2 Malcolm McLean napisał(a):
> > > > On Saturday, 5 August 2023 at 11:20:47 UTC+1, fir wrote:
> > > > > sobota, 5 sierpnia 2023 o 11:59:22 UTC+2 Malcolm McLean napisał(a):
> > > > > > I've been working on the Baby X resource compiler for some time now. I've added in support for audio, unicode, and dataframes, plus a few minor enhancements such as the ability to add comments and write out a header as well as a C source file.
> > > > > >
> > > > > > I'm thinking of declaring a version shortly. Then I'll probably rest from my labours. Anything else anyone would want to see?
> > > > > >
> > > > > > I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help..
> > > > > >
> > > > > > The code is at
> > > > > > https://github.com/MalcolmMcLean/babyxrc
> > > > > give some examples of how it work or something...
> > > > > usenet is for discussint the matter things (at least in core)..
> > > > >
> > > > > also imo people shoudl genrally asume that usenet is not
> > > > > for opening links so people shouldnt post links to much imo
> > > > > but if they post about something paste it as a text content
> > > > >
> > > > It's a resource compiler. So it has a similar function to the resource compilers
> > > > included in Visual Studio or XCode. However instead of packaging the resources
> > > > into an opaque binary blob which can only be read by that platform, it
> > > > produces portable ANSI C output files which can be read anywhere.
> > > >
> > > > So you write a little script file. If you want to include an image, it reads it and
> > > > spits out a 32 bit rgba buffer. If you want an audio clip, it spits out a list
> > > > of pcm values as shorts. If you want a string, it escapes it for you and spits out
> > > > a C string.
> > > >
> > > > However its strength is that it also allows for a bit of processing of data. So
> > > > images can be resized, or audio can be re-sampled to match the rate you want
> > > > in your program. Text can be taken in in one fomart and output in another, so
> > > > you can read ina UTF-8 file and have a UTF-16 string output. There's also a
> > > > brand new and experimental dataframe tag which loads a CSV file and produces
> > > > an array of C structs.
> > > >
> > > > Here's a script file
> > > >
> > > > <BabyXRC>
> > > > <string name = "hellobabyx">Hello &quot;Baby X&quot;</string>
> > > > </BabyXRC>
> > > >
> > > > Invoke the program like this
> > > >
> > > > babyxrc hellobabyx.xml
> > > >
> > > > Here's the output
> > > >
> > > > char *hellobabyx = "Hello \"Baby X\"";
> > > and what it do with images? or things like fonts?? make char* array with initialiser or what?
> > >
> > <BabyXRC>
> > <image src = "testimage.jpeg"></image>
> > <image name = "resizedimage" src = "image2.png" width = "256" height = "256"></image>
> > </BabyXRC>
> >
> > This one is converting two images to C source.
> > The first is a jpeg. It loads it, the saves the data as a C array representing 32 bit rgba values.
> > The second is a png. However we want to give it a different name andd we want to resize it
> > to 256 x 256.
> overally there is a question how usage of this resources as a /data section in exe is good... in green fire for example i used bitmap fonts nad put it into it then after all i found this bad and began to use a code which uses ttf fonts but 'stamped' in internal bitmap..no chance to beat the work of fontmakers imo those the people who made unparalelable work imo
>
> overaly systems and their filesystems are weird this times imo they lack of order and restriction..overally it alweys makes me weird why those sytems ale o liberal and chaotic though not to say for some reasons this is better than my own style of doing things becouse if i would be dong thing it all would be more simple and probably restricted which im not sure is good - becouse my thinking tend to be rectangular, i think i would never invent such style as c has which more resembles me style of a plant, or something liek that

imo filesystem probably should be build using concept of being 'modular'....i think probably each file should be treated as a module..
and the modules should probably 'carry' the scheme of references..
for exampel some should be 'open' some only tied to other module and 'closed'.. there is yet a problem of versioning..i think for example non compatible versions should be named like "A" "B" "C" when numbers only have secondary meaning and denote internal changes

besides this i think there could be a concept of 'packs' and 'locations'

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

>I don't have a Linux machine. If someone would be kind enough to valgrind it to check for memory leaks or worse bugs, that would be a help.
>

If you have a windows machine, you have a linux machine, simply download
the free WSL.

https://learn.microsoft.com/en-us/windows/wsl/install

In article <P9tzM.486505$GMN3.64036@fx16.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
>Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
>
>>I don't have a Linux machine. If someone would be kind enough to
>>valgrind it to check for memory leaks or worse bugs, that would be a
>>help.
>>
>
>If you have a windows machine, you have a linux machine, simply
>download the free WSL.

From everything I've heard, WSL/WSL2 is whack.

Much better to install Virtual Box and go that route.

--
https://en.wikipedia.org/wiki/Mansplaining

It describes comp.lang.c to a T!

gazelle@shell.xmission.com (Kenny McCormack) writes:
>In article <P9tzM.486505$GMN3.64036@fx16.iad>,
>Scott Lurndal <slp53@pacbell.net> wrote:
>>Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
>>
>>>I don't have a Linux machine. If someone would be kind enough to
>>>valgrind it to check for memory leaks or worse bugs, that would be a
>>>help.
>>>
>>
>>If you have a windows machine, you have a linux machine, simply
>>download the free WSL.
>
>From everything I've heard, WSL/WSL2 is whack.

Well, if you're relying on the same "everything you've heard"
about Dijkstra, then perhaps you should evaluate WSL
yourself first. :-)

In article <CWvzM.295629$U3w1.196231@fx09.iad>,
Scott Lurndal <slp53@pacbell.net> wrote:
....
>Well, if you're relying on the same "everything you've heard"
>about Dijkstra, ....

I think you have confused me with Malcolm.

(FWW, if Dijkstra was/is a "lefty", that would be all to the good)

--
I voted for Trump because I thought he'd make pussy grabbing legal.
I honestly don't see any other way America could be made great again.

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> On Saturday, 5 August 2023 at 12:17:46 UTC+1, Ben Bacarisse wrote:
>> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>>
>> > I've been working on the Baby X resource compiler for some time now.
>> ...
>> > I don't have a Linux machine. If someone would be kind enough to
>> > valgrind it to check for memory leaks or worse bugs, that would be a
>> > help.
>> The README has no build instructions. I'm happy to guess, but other
>> users might not be.
>>
> Thanks.
> Yes, one problem is that when you are both the developer and doumenter,
> you're so close to the project that it's eay to miss the obvious.

I get compile errors, but maybe this is not the right place to debug a
build system...

--
Ben.

On Saturday, 5 August 2023 at 20:33:48 UTC+1, Ben Bacarisse wrote:
> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>
> > On Saturday, 5 August 2023 at 12:17:46 UTC+1, Ben Bacarisse wrote:
> >> Malcolm McLean <malcolm.ar...@gmail.com> writes:
> >>
> >> > I've been working on the Baby X resource compiler for some time now.
> >> ...
> >> > I don't have a Linux machine. If someone would be kind enough to
> >> > valgrind it to check for memory leaks or worse bugs, that would be a
> >> > help.
> >> The README has no build instructions. I'm happy to guess, but other
> >> users might not be.
> >>
> > Thanks.
> > Yes, one problem is that when you are both the developer and doumenter,
> > you're so close to the project that it's eay to miss the obvious.
> I get compile errors, but maybe this is not the right place to debug a
> build system...
>
Oh dear.
Can you raise an issue on the github page?
It compiles for me on Mac and Windows without problems.

Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> On Saturday, 5 August 2023 at 20:33:48 UTC+1, Ben Bacarisse wrote:
>> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>>
>> > On Saturday, 5 August 2023 at 12:17:46 UTC+1, Ben Bacarisse wrote:
>> >> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>> >>
>> >> > I've been working on the Baby X resource compiler for some time now.
>> >> ...
>> >> > I don't have a Linux machine. If someone would be kind enough to
>> >> > valgrind it to check for memory leaks or worse bugs, that would be a
>> >> > help.
>> >> The README has no build instructions. I'm happy to guess, but other
>> >> users might not be.
>> >>
>> > Thanks.
>> > Yes, one problem is that when you are both the developer and doumenter,
>> > you're so close to the project that it's eay to miss the obvious.
>> I get compile errors, but maybe this is not the right place to debug a
>> build system...
>>
> Oh dear.
> Can you raise an issue on the github page?

Can you find a Linux user of BabyX who might want to try it? Since I'm
not a potential user, there's not much incentive to start what might be
a long debugging session.

> It compiles for me on Mac and Windows without problems.

--
Ben.

On Saturday, 5 August 2023 at 22:48:46 UTC+1, Ben Bacarisse wrote:
> Malcolm McLean <malcolm.ar...@gmail.com> writes:
>
> > On Saturday, 5 August 2023 at 20:33:48 UTC+1, Ben Bacarisse wrote:
> >> Malcolm McLean <malcolm.ar...@gmail.com> writes:
> >>
> >> > On Saturday, 5 August 2023 at 12:17:46 UTC+1, Ben Bacarisse wrote:
> >> >> Malcolm McLean <malcolm.ar...@gmail.com> writes:
> >> >>
> >> >> > I've been working on the Baby X resource compiler for some time now.
> >> >> ...
> >> >> > I don't have a Linux machine. If someone would be kind enough to
> >> >> > valgrind it to check for memory leaks or worse bugs, that would be a
> >> >> > help.
> >> >> The README has no build instructions. I'm happy to guess, but other
> >> >> users might not be.
> >> >>
> >> > Thanks.
> >> > Yes, one problem is that when you are both the developer and doumenter,
> >> > you're so close to the project that it's eay to miss the obvious.
> >> I get compile errors, but maybe this is not the right place to debug a
> >> build system...
> >>
> > Oh dear.
> > Can you raise an issue on the github page?
> Can you find a Linux user of BabyX who might want to try it? Since I'm
> not a potential user, there's not much incentive to start what might be
> a long debugging session.
> > It compiles for me on Mac and Windows without problems.
>
I've found the bug. Whilst you're right that here isn't the right place to
do a build debug session, Bart would love this. A third party module is
using the stdint.h type unit64_t and this is clashing with a symbol defined
elsewhere.
So the entire Baby X resource compiler program becomes usable on Linux.

In article <a4b1ffc5-2ec6-463e-8c69-bb41c6f4f38cn@googlegroups.com>,
Malcolm McLean <malcolm.arthur.mclean@gmail.com> wrote:
....
>I've found the bug. Whilst you're right that here isn't the right place to
>do a build debug session, Bart would love this. A third party module is
>using the stdint.h type unit64_t and this is clashing with a symbol defined
>elsewhere.

unit64_t?

Sounds like something out of a sci-fi novel...

>So the entire Baby X resource compiler program becomes usable on Linux.

Usable? (or unusable)

--
I voted for Trump because I thought he'd make pussy grabbing legal.
I honestly don't see any other way America could be made great again.

On Sunday, 6 August 2023 at 12:01:28 UTC+1, Kenny McCormack wrote:
> In article <a4b1ffc5-2ec6-463e...@googlegroups.com>,
> Malcolm McLean <malcolm.ar...@gmail.com> wrote:
> ...
> >I've found the bug. Whilst you're right that here isn't the right place to
> >do a build debug session, Bart would love this. A third party module is
> >using the stdint.h type unit64_t and this is clashing with a symbol defined
> >elsewhere.
> unit64_t?
>
> Sounds like something out of a sci-fi novel...
> >So the entire Baby X resource compiler program becomes usable on Linux.
> Usable? (or unusable)
>
Unusable. It's usable now. There wasn't much wrong with it. But just enough
so that it wont compile. And that will put large numbers of potential users off.
I didn't have a clue until Ben kindly told me. I've got an Apple Mac and a Windows
machine, but not currently a Linux machine.
The a basic problem was that I am using a MP3 decoder written by someone else.
They wrote a file called clib.h which has various efficiency and portability hacks.
It includes this

#if !NEED_MINILIBC
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#endif
#include <math.h>

#ifndef __int8_t_defined
#define __int8_t_defined
typedef unsigned char uint8_t;
typedef signed char int8_t;
typedef unsigned short uint16_t;
typedef signed short int16_t;
typedef unsigned int uint32_t;
typedef signed int int32_t;
#ifdef _MSC_VER
typedef unsigned __int64 uint64_t;
typedef signed __int64 int64_t;
#else
typedef unsigned long long uint64_t;
typedef signed long long int64_t;
#endif
#endif

Linux include <stdint.h> from the system headers. Windows and Mac doesn't.
So this breaks when compiled on Linux. By trying to be portable, they managed
to produce something which wasn't portable.

It really confirms my view that it's best to write in a conservative subset of C90
and the subsequent standards. otherwise you just get endless trouble. But writing
my own MP3 decoder would be a huge job (I've written one before, but it was for
work so of course I can't put it on the web).

On Sun, 6 Aug 2023 04:36:47 -0700 (PDT)
Malcolm McLean <malcolm.arthur.mclean@gmail.com> wrote:
> The a basic problem was that I am using a MP3 decoder written by someone else.
> They wrote a file called clib.h which has various efficiency and portability hacks.
> It includes this
>
> #if !NEED_MINILIBC
> #include <stdio.h>
> #include <stdlib.h>
> #include <string.h>
> #endif
> #include <math.h>
>
> #ifndef __int8_t_defined
> #define __int8_t_defined
> typedef unsigned char uint8_t;
> typedef signed char int8_t;
> typedef unsigned short uint16_t;
> typedef signed short int16_t;
> typedef unsigned int uint32_t;
> typedef signed int int32_t;
> #ifdef _MSC_VER
> typedef unsigned __int64 uint64_t;
> typedef signed __int64 int64_t;
> #else
> typedef unsigned long long uint64_t;
> typedef signed long long int64_t;
> #endif
> #endif
>
> Linux include <stdint.h> from the system headers. Windows and Mac doesn't.
> So this breaks when compiled on Linux. By trying to be portable, they
> managed to produce something which wasn't portable.
>
> It really confirms my view that it's best to write in a conservative subset
> of C90 and the subsequent standards. otherwise you just get endless
> trouble.

My view is that it's best not to use code which has so many issues unless you
fix them first. First , the code above has undefined behaviour because it
uses reserved identifiers. Second , using __ in the beginning of
identifiers with the hope of avoiding clashes is a bad design decision
because so many C libraries make the same bad decision so it does not reduce
the chances of having clashes. It is best to start identifiers in libraries
which are for public usage with a prefix which isn't reserved by the standard
and has a reasonable chance of being unique. So for example an MP3 decoder
written by John Smith could start all public identifiers with JSMD_ (John
Smith MP3 decoder).

--
vlaho.ninja/prog