Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion interpreter.c split
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dan Sugalski  
View profile  
 More options Apr 7 2004, 2:48 pm
Newsgroups: perl.perl6.internals
From: d...@sidhe.org (Dan Sugalski)
Date: Wed, 7 Apr 2004 14:07:17 -0400
Local: Wed, Apr 7 2004 2:07 pm
Subject: Re: interpreter.c split
At 10:24 AM +0200 4/7/04, Leopold Toetsch wrote:

>I'd like to separate functions of interpreter.c into distinct files
>(it's currently more then 2500 lines):

>init ... init destroy
>cb   ... callback function handling
>run_loop ... runloop selection
>run_fromc ... call runloop from c
>load_ops  ... dynamic oplib loading
>...

>Which scheme should be used:
>- interp/*.c  (subsystem directory)
>- src/interp_*.c  (8+3 filename problems?)
>- ??

How 'bout:

    src/
        runloop.c - runloop stuff, including calling in
        interpreter.c - interpreter setup, destruction, cloning, and whatnot
        oplibs.c - oplib loading, unloading, and management
--
                                         Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
d...@sidhe.org                         have teddy bears and even
                                       teddy bears get drunk


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.