Brent Dax wrote:
[...]
> The code could look like this:
>
> (pull in hints file)
> if(-e "Parrot/Config.pm") {
> eval "use Parrot::Config";
> %c=%pConfig;
> }
> (etcetera)
>
> except that "Parrot/Config.pm" isn't portable to VMS.
I
Brent Dax wrote:
>
> Dan Sugalski:
> # At 06:43 PM 9/20/2001 -0700, Brent Dax wrote:
> # >Stefan Dragnev:
> # ># - $c{cc_denug} = ' ';
> # ># + $c{cc_debug} = ' ';
> # >
> # >So *that*'s why -g kept appearing...thanks, applied.
> #
> # Don't forget that debugging isn't always -g. (It'
Brent Dax wrote:
[...]
>
> +sub buildfile {
> + my($filename)=shift;
> +
> + local $/;
> + open(IN, "<$filename.in");
According to the coding guidelines PDD (which still doesn't seem
to have been assigned a PDD number), filenames shouldn't have more
than one '.' in them. I kno
Simon Cozens wrote:
[...]
> I'm just not sure it's fair on Old World hackers. Will there be a way to stop
> Perl upgrading stuff to Unicode on the way in?
and I'm probably not the only Old World hacker that would
prefer a build option to simply eliminate Unicode support altogether...
