Re: [Arsperl-devel] ARSperl package structure changes

[Georg G. <ggr...@gm...>]

Hi,

h2ph_pre.ph and artypes.ph look the same on my linux workstation in between
(1;, with a comment in artypes.ph that you should not remove this hack :D).

It would be "cleaner" if you change to ARS.pm and ARS:: modules. I'm not
sure about the advantages you'd gain though, except that you have a
different package structure then. I don't think that you'll need
polymorphism, so you'll probably not gain an advantage out of this.

Kind regards,
Georg

On Wed, Apr 1, 2009 at 9:58 AM, Thilo Stapff <thi...@ap...>wrote:

> >
> > The "ARS::AR_SORT_ASCENDING" business comes from those files. Those
> > files are supposedly to be generated by Makefile.PL during the build
> > process. The intention is to give people mnemonic access to header
> > constants without having them rely on "ars_export(..., 1 | 2 | 8 |
> > 4096)" messiness.
> >
>
> Are you sure? On my system (Windows XP), "_h2ph_pre.ph" and "artypes.ph"
> are almost empty. They contain only the statement "1;" so that they can
> be successfully loaded. The ARS::AR_XXXX_YYYYY constants are defined in
> ARSar-h.pm (which is also generated by Makefile.PL). Are things
> generated differently on Unix systems?
>
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Arsperl-devel mailing list
> Ars...@ar...
> https://lists.sourceforge.net/lists/listinfo/arsperl-devel
>