To facilitate DSet extensions, we treat any distributed object type that

ends in Set as a DSet. This is not optimal, but writing a full blown
parser so that we can analyze the inheritance hierarchy of the files we're
processing to determine for sure that something extends DSet would be at
least an order of magnitude greater pain in the ass than just doing simple
textual processing. We'll leave that up to future people.


git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@1232 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
Michael Bayne
2002-04-11 19:11:07 +00:00
parent 462724f82d
commit 3f1a21f76c
+3 -3
View File
@@ -1,6 +1,6 @@
#!/usr/bin/perl -w
#
# $Id: gendobj,v 1.11 2002/03/19 01:10:02 mdb Exp $
# $Id: gendobj,v 1.12 2002/04/11 19:11:07 mdb Exp $
#
# gendobj is used to generate DObject source file definitons basded on
# abbreviated declarations. Because DObject fields all have standard
@@ -161,7 +161,7 @@ sub print_dobj_setters
$cfield =~ s/(\w)/\U$1/;
# some known types have special setters
if ($type eq "DSet") {
if ($type =~ ".*Set") {
print OUT <<EOF;
/**
@@ -204,7 +204,7 @@ sub print_dobj_setters
* change. Proxied copies of this object (on clients) will apply the
* value change when they received the attribute changed notification.
*/
public void set$cfield (DSet $field)
public void set$cfield ($type $field)
{
this.$field = $field;
requestAttributeChange($fcode, $field);