I have just made a new release of the YARD parser at http://www.sf.net/projects/yard-parser/ , which fixes a lot of the microsoft specific dependencies.

-- 
Christopher Diggins
Object Oriented Template Library (OOTL)
http://www.ootl.org

No makefiles, project files, readme.

Where does one start?

"christopher diggins" <cdiggins@videotron.ca> wrote in message news:d050g9$ejl$1@digitaldaemon.com...
>I have just made a new release of the YARD parser at http://www.sf.net/projects/yard-parser/ , which fixes a lot of the microsoft specific dependencies.
>
> -- 
> Christopher Diggins
> Object Oriented Template Library (OOTL)
> http://www.ootl.org
> 

Whoops, sorry.

Added a project file. http://sourceforge.net/project/showfiles.php?group_id=126822&package_id=139243&release_id=309752

-- 
Christopher Diggins
Object Oriented Template Library (OOTL)
http://www.ootl.org

Hi,

Just out of curiosity, I now see that Yard requires OOTL, I thought that it was supposed to be independent of other libraries.

I got it to compile under Visual Studio but not after changing the paths.

Zz
"christopher diggins" <cdiggins@videotron.ca> wrote in message
news:d058v4$nq5$1@digitaldaemon.com...
> Whoops, sorry.
>
> Added a project file.
>
http://sourceforge.net/project/showfiles.php?group_id=126822&package_id=139243&release_id=309752
>
> -- 
> Christopher Diggins
> Object Oriented Template Library (OOTL)
> http://www.ootl.org
>
>

"Zz" <Zz@Zz.com> wrote in message news:d05eoi$vi2$1@digitaldaemon.com...
> Hi,
>
> Just out of curiosity, I now see that Yard requires OOTL, I thought that
> it
> was supposed to be independent of other libraries.

YARD itself should only need char_set. I should probably move char_set back into the YARD namespace, I just can't make up my mind. Apart from this the tests themselves need other parts of the OOTL.

> I got it to compile under Visual Studio but not after changing the paths.

Is this a bad thing I did? How should I deal with this? I am new to sharing libraries of code with other people.

Did it pass the tests successfully? Would you mind trying to compile it under Metrowerks as well?

Thanks!

-- 
Christopher Diggins
Object Oriented Template Library (OOTL)
http://www.ootl.org

Hi,

> YARD itself should only need char_set. I should probably move char_set
back
> into the YARD namespace, I just can't make up my mind. Apart from this the tests themselves need other parts of the OOTL.
>
> > I got it to compile under Visual Studio but not after changing the
paths.
>
> Is this a bad thing I did? How should I deal with this? I am new to
sharing
> libraries of code with other people.

I just move the stuff up so that ../../cpp can be found. (I'm a CodeWarrior
user).

> Did it pass the tests successfully? Would you mind trying to compile it under Metrowerks as well?

Under Visual Studio the tests compiled passed.

CodeWarrior complains of a lot of things I actually get 100 errors and 17
warnings.
It also fails under Intel's compiler.

Zz.

For grins, I just ran it on a suite of compilers.

It's got a lot of problems, including:

    - uses non-standard std::exception::exception(char const *) ctor
    - uses undiscriminated #pragma once
    - plenty of missing typename type qualifiers
    - etc. etc.

I'd have to do a full run to get you all the details, but I suggest your best course of action is to get DMC++ 8.42beta and/or GCC 3.4 and ensure that it at least compilers with that/them along with VC++ 7.1. Once you've got that done, I'll lend a hand and get it compiling on the rest of the (Win32) majors. :-)

btw, I note you're using statics. Makes it non-thread-safe. You might want to check out the spin mutex technique in Chapters 10+11 of Imperfect C++. (STLSoft has spin mutexes, in both WinSTL and UNIXSTL.)

Cheers

Matthew

"christopher diggins" <cdiggins@videotron.ca> wrote in message news:d050g9$ejl$1@digitaldaemon.com...
>I have just made a new release of the YARD parser at http://www.sf.net/projects/yard-parser/ , which fixes a lot of the microsoft specific dependencies.
>
> -- 
> Christopher Diggins
> Object Oriented Template Library (OOTL)
> http://www.ootl.org
> 

"christopher diggins" <cdiggins@videotron.ca> wrote in message news:d05g94$11dt$1@digitaldaemon.com...
> "Zz" <Zz@Zz.com> wrote in message news:d05eoi$vi2$1@digitaldaemon.com...
>> Hi,
>>
>> Just out of curiosity, I now see that Yard requires OOTL, I thought
>> that it
>> was supposed to be independent of other libraries.
>
> YARD itself should only need char_set. I should probably move char_set back into the YARD namespace, I just can't make up my mind. Apart from this the tests themselves need other parts of the OOTL.
>
>> I got it to compile under Visual Studio but not after changing the paths.
>
> Is this a bad thing I did? How should I deal with this? I am new to sharing libraries of code with other people.

It should have a single make file that is used to build the libs (if any), the test file, and execute the test file.

Right now I'm using one of my tools - tmpl2make.py - to generate makefiles for Win32 and UNIX (for Borland, CodeWarrior, Comeau, DMC++, GCC, Intel, Visual C++, Watcom). It takes a template and a tools file (XML describing what tools there are, and what capabilities they have), and spits out makefiles (e.g. "makefile" for Borland/DMC++/VC++, "makefile.win32" + "makefile.unix" for CodeWarrior/Comeau/GCC/Intel)

The makefile should either be all relative, i.e. its -I commands are like -I../../include, or you should assume (and discriminate for, with MAKEs that can do so) the definition of environment/make cmd-line variables. You should _not_ have any absolutes.

Also, it's been my experience that one must step away from the IDDE (esp. VC++ .NET) as soon as possible, as it just makes this whole process more painful in the long run. (I still use such libs within IDEs, but with projects that do not necessarily form part of the distribution, and which certainly do not form part of the automated build/test/release process.)

I'd be happy to share (privately) the script with you, but it's not for public dissemination because it's, er, a bit scrappy. ;)

"Matthew" <admin@stlsoft.dot.dot.dot.dot.org> wrote in message news:d05r59$1dfo$1@digitaldaemon.com...
> For grins, I just ran it on a suite of compilers.
>
> It's got a lot of problems, including:
>
>    - uses non-standard std::exception::exception(char const *) ctor
>    - uses undiscriminated #pragma once
>    - plenty of missing typename type qualifiers
>    - etc. etc.

Damn Microsoft. I really chose the wrong compiler to get familiar with. I miss the good old days of Turbo Pascal.

> I'd have to do a full run to get you all the details, but I suggest your best course of action is to get DMC++ 8.42beta and/or GCC 3.4 and ensure

Okay then. I am going to use VC++ from now on as a last resort.

> that it at least compilers with that/them along with VC++ 7.1. Once you've got that done, I'll lend a hand and get it compiling on the rest of the (Win32) majors. :-)

Thanks.

> btw, I note you're using statics. Makes it non-thread-safe. You might want to check out the spin mutex technique in Chapters 10+11 of Imperfect C++. (STLSoft has spin mutexes, in both WinSTL and UNIXSTL.)

Sorry, but I don't own your book, I am poor as a pauper. Is thread-safety a requirement of STLSoft inclusion? I am not an expert in techniques for thread-safety, isn't it an enormous amount of work to write and test code for thread-safety? Or would spin mutexes automatically solve that problem? My personal preference is to ignore multi-threaded use scenarios.

> Cheers
>
> Matthew

Thanks for you help.

-- 
Christopher Diggins
Object Oriented Template Library (OOTL)
http://www.ootl.org

"Matthew" <admin@stlsoft.dot.dot.dot.dot.org> wrote in message news:d05rnd$1duk$1@digitaldaemon.com...
>
> "christopher diggins" <cdiggins@videotron.ca> wrote in message news:d05g94$11dt$1@digitaldaemon.com...
>> "Zz" <Zz@Zz.com> wrote in message news:d05eoi$vi2$1@digitaldaemon.com...
>>> Hi,
>>>
>>> Just out of curiosity, I now see that Yard requires OOTL, I thought that
>>> it
>>> was supposed to be independent of other libraries.
>>
>> YARD itself should only need char_set. I should probably move char_set back into the YARD namespace, I just can't make up my mind. Apart from this the tests themselves need other parts of the OOTL.
>>
>>> I got it to compile under Visual Studio but not after changing the paths.
>>
>> Is this a bad thing I did? How should I deal with this? I am new to sharing libraries of code with other people.
>
> It should have a single make file that is used to build the libs (if any), the test file, and execute the test file.
>
> Right now I'm using one of my tools - tmpl2make.py - to generate makefiles for Win32 and UNIX (for Borland, CodeWarrior, Comeau, DMC++, GCC, Intel, Visual C++, Watcom). It takes a template and a tools file (XML describing what tools there are, and what capabilities they have), and spits out makefiles (e.g. "makefile" for Borland/DMC++/VC++, "makefile.win32" + "makefile.unix" for CodeWarrior/Comeau/GCC/Intel)
>
> The makefile should either be all relative, i.e. its -I commands are like -I../../include, or you should assume (and discriminate for, with MAKEs that can do so) the definition of environment/make cmd-line variables. You should _not_ have any absolutes.
>
> Also, it's been my experience that one must step away from the IDDE (esp. VC++ .NET) as soon as possible, as it just makes this whole process more painful in the long run. (I still use such libs within IDEs, but with projects that do not necessarily form part of the distribution, and which certainly do not form part of the automated build/test/release process.)
>
> I'd be happy to share (privately) the script with you, but it's not for public dissemination because it's, er, a bit scrappy. ;)


I don't have a python interpreter, but this gives me some excellent ideas. My next release will have make files.

Thanks!

-- 
Christopher Diggins
Object Oriented Template Library (OOTL)
http://www.ootl.org